The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #13514

Forge should enforce versions being semantic

Added by Matt Robinson about 2 years ago. Updated almost 2 years ago.

Status:ClosedStart date:03/29/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-Spent time:-
Target version:-
Keywords: Affected URL:
Branch:https://github.com/mmrobins/puppet-forge/tree/ticket/master/13514-enforce_semantic_versioning

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

This means module data cleanup will need to be done, and that new modules uploaded should only be allowed if their release version is semantic.


Related issues

Related to Puppet Forge - Feature #3775: Site should extract, use and display release version and ... Closed 05/15/2010

History

#1 Updated by Matt Robinson about 2 years ago

  • Branch set to https://github.com/mmrobins/puppet-forge/tree/ticket/master/13514-enforce_semantic_versioning

The attached branch includes a migration to cleanup version data in both the database and tarballs. Coming soon are changes so that the versions don’t get into this state again.

#2 Updated by Michael Arnold almost 2 years ago

I tripped over this when I first started using the Forge. I could create and upload modules with my YearMonthDay version string, but PMT wouldn’t download them until I succumbed to SemVer.

#3 Updated by Ken Barber almost 2 years ago

  • Status changed from Accepted to Closed

#4 Updated by Ken Barber almost 2 years ago

This was merged already. Closed.

Also available in: Atom PDF