Skip to content

The release script does not handle versions properly

For example it has increased bob.extension from 2.4.5 to 3.4.5 where it should have been 3.0.0

I haven't checked other packages but I imagine this is the case elsewhere.

  • The tag changelogs on gitlab are markdown not rst. It would be proper to call the file changelog_since_last_release.md instead.
  • The release script should use bob_new_version script to avoid issues like this in future. If the script is not flexible enough, we can easily change it.
  • It would have been better to also point to merge requests in the changelogs. This way you can click in Gitlab's interface and see the actual code change easily.
  • The default tag for packages without any tag should be 0.0.1 instead of 1.0.0. Making a package version 1 means that the author will follow strict semantic versioning from now and the package is stable: https://semver.org/ However, this is not true at all.
  • Most packages (with only CI changes) should have gotten a patch version instead of minor.
  • The tags need to be sorted based on their version not their latest date.
  • The versions need to be bumped correctly.
  • Deprecate the new_version script in bob.extension.
Edited by Amir MOHAMMADI