Tag 2.17.0 set to invalid commit

Bug #1857017 reported by Damir
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cliff
Fix Released
Undecided
Unassigned

Bug Description

In change https://review.opendev.org/#/c/698485 the tag 2.17.0 was installed on the commit made on Mar 14, 2018 (8bcd068).
At the same time, version 2.16.0 points to the newer commit made on Sep 6, 2019 (6b6b186).
It looks like it was done by mistake.

At least constraints for cmd2 in requirements.txt were deleted - `cmd2>=0.8.0,!=0.8.3,<0.9.0 # MIT` .

Damir (saydamir)
description: updated
Revision history for this message
Sean McGinnis (sean-mcginnis) wrote :

New release will need to be proposed to more recent commit. This is not a bug in cliff.

Revision history for this message
Damir (saydamir) wrote :

Are you sure that should be release version - not RC or beta?
2.17.0 tries to use the newest version of cmd2(+0.9), but it was restricted in change https://review.opendev.org/#/c/629269 .

Revision history for this message
Damir (saydamir) wrote :

It turned out that version 2.17.0 pointed to the wrong commit, and now we have correct version in release 2.18.0 - https://review.opendev.org/#/c/701405/ .

Changed in python-cliff:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.