Fix semantic versioning parsing #7
No reviewers
Labels
No Label
Priority
Critical
Priority
High
Priority
Low
Priority
Normal
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Type
Breaking
Type
Documentation
Type
Enhancement
Type
Feature
Type
Report
Type
Security
Type
Suggestion
Type
Testing
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/extensions-website#7
Loading…
Reference in New Issue
No description provided.
Delete Branch "dfelinto/extensions-website:fix-version"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The original parser was failing at handling 2.9.3-alpha. And although I
could fix the regex, this patch implements a complete semantic version
support instead, and uses the 'semantic_version' Python module natively
as much as possible.
Note that although this uses the semantic_version library as much as
possible, it has still to implement its own Field to make it
serializable.
The old migrations files had to be updated because the new
VersionStringField will only accept semantic version values (e.g., the
old 0.1 entries would fail now).
On top of that as part of the latest migration we update all the
version-like fields to be compliant with the semantic version. So
existing databases are validated once they migrate.
These models are:
Remember to ./manage.py migrate after pulling this commit.
How add-ons can have a "-alpha" version, as well as Blender:
70dc621710
tobe1b36b2db
be1b36b2db
to79cdd560a7