development version strings are not semver compatible

Open
#682 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, python
Domain
build-system, release

Research direction

Start by locating the GitHub Actions automation in the plugin template that generates development version strings, then inspect how it produces values like 3.17.0.dev. Done means development pre-release versions follow Python's PEP 440 requirements and remain semver compatible; verify the generated version in the relevant workflow or tests.

Written by the indexing model from the issue text.

Description

The GHA automation from the plugin template produces a dev version number like 3.17.0.dev which is not semver compatible nor is it Python version spec compatible, see pre releases.

It would be good if our pre releases used Python compliant versions.

Dominant language
Python
Stars
10
Forks
40
Avg merge
21h 24m
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pulp/plugin_template

All issues in pulp/plugin_template

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.