Issue #4936
Ruby client version labelling is incorrect with respect to "most recent" versions
Description
The ruby client versions with the 3.0.0rc2.dev.* labels are considered as earlier than 3.0.0rc2 versioned releases.
it appears that the ruby gem tools, bundler, et al, consider the "dev" labels as being older when in fact the "3.0.0rc2" labelled gems are older.
You can verify by opening an irb console:
irb(main):010:0> Gem::Version.new("3.0.0rc2") > Gem::Version.new("3.0.0rc2.dev.1559765173")
=> true
When a gem version is not specified in a Gemfile or in a .gemspec file, the default version installed and used will be the latest available, in this case the version labelled "3..0.0rc2".
Associated revisions
Revision 26f8233d
View on GitHub
Set version to .dev for the master branch
A correct version would be shown for installations from the master branch. Bindings will be generated with a proper version as well.
Revision baca70f1
View on GitHub
Set version to .dev for the master branch
A correct version would be shown for installations from the master branch. Bindings will be generated with a proper version as well.
Revision 07805594
View on GitHub
Set version to .dev for the master branch
A correct version would be shown for installations from the master branch. Bindings will be generated with a proper version as well.
Revision 07805594
View on GitHub
Set version to .dev for the master branch
A correct version would be shown for installations from the master branch. Bindings will be generated with a proper version as well.
Revision 07805594
View on GitHub
Set version to .dev for the master branch
A correct version would be shown for installations from the master branch. Bindings will be generated with a proper version as well.
Revision 07805594
View on GitHub
Set version to .dev for the master branch
A correct version would be shown for installations from the master branch. Bindings will be generated with a proper version as well.
Revision d42ea19d
View on GitHub
Set version to .dev for the master branch
A correct version would be shown for installations from the master branch. Bindings will be generated with a proper version as well.
Revision 8ca40be7
View on GitHub
Set version to .dev for the master branch
A correct version would be shown for installations from the master branch. Bindings will be generated with a proper version as well.
History
#1
Updated by amacdona@redhat.com over 1 year ago
- Triaged changed from No to Yes
- Sprint set to Sprint 54
#2
Updated by ttereshc over 1 year ago
- Status changed from NEW to ASSIGNED
#3
Updated by ttereshc over 1 year ago
- Assignee set to ttereshc
#4
Updated by ttereshc over 1 year ago
- Status changed from ASSIGNED to POST
Plugins' versions changes
https://github.com/pulp/pulp_file/pull/241
https://github.com/pulp/pulp_rpm/pull/1376
https://github.com/pulp/pulp_ansible/pull/114
https://github.com/pulp/pulp_docker/pull/365
https://github.com/pulp/pulp_maven/pull/13
Travis changes
https://github.com/pulp/plugin_template/pull/52
#5
Updated by ttereshc over 1 year ago
- Status changed from POST to MODIFIED
Applied in changeset plugin_template|930bf2afc504fb4a1ae86ba0e7a8b7b054e1dbab.
#6
Updated by ttereshc over 1 year ago
- Status changed from MODIFIED to POST
#7
Updated by ttereshc over 1 year ago
- Status changed from POST to MODIFIED
#8
Updated by bmbouter about 1 year ago
- Sprint/Milestone set to 3.0.0
#9
Updated by bmbouter about 1 year ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Please register to edit this issue
.
Don't add .dev release part of the version
It should be done by Pulp 3 plugins themselves. Their master branch should contain .dev release segment in the version identifier of the upcoming release.
closes #4936 https://pulp.plan.io/issues/4936