Skip to content

Release pipeline: Sanity check before accepting a version number #84

Description

@hartym

While releasing, no check is done on version number. Add the following:

  • If version is lower than current, warn the user he's probably making a mistake and ask for "hard" confirmation.
  • If version is equal to current, warn and refuse if already pushed
  • If there is a version jump, warn
  • Add default ? Next patch ?
  • Add "patch"/"p", "minor"/"m", "major"/"M" string to compute the version instead of typing it.
Current version: 0.5.8 Git version: 0.5.8
Next version? 0.5.9

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions