Draft
Conversation
✅ Deploy Preview for nifty-bassi-e26446 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Co-authored-by: phlax <454682+phlax@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix version parsing for post-release versions in jq
Add Sep 11, 2026
.postN support to utils::version
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
jq/utils.jqonly handled strictMAJOR.MINOR.PATCH[-dev]versions, so0.4.13.post0[-dev]failed parsing and brokeactions/versionconsumers on theworkspacebranch. This change extends version parsing and next-version calculation to support PEP 440-style post releases without changing plain-version behavior.Version parsing
utils::versionto acceptMAJOR.MINOR.PATCH[.postN][-dev]postto the output shape (numberornull)Next-version semantics
X.Y.Z-dev -> X.Y.ZX.Y.Z -> X.Y.(Z+1)-devX.Y.Z.postN-dev -> X.Y.Z.postNX.Y.Z.postN -> X.Y.Z.post(N+1)-devError handling
tonumberfailure with an explicit error for unsupported version stringsFixtures
post: nullactions/versionfixture covering0.4.13.post0Example:
{ "version": "0.4.13.post0", "is_dev": false, "major": 0, "minor": 4, "patch": 13, "post": 0, "next": "0.4.13.post1-dev" }Note:
workspacebranch workflows will need to bump theirenvoyproxy/toolshed/actions/*pins to anactions-v*release containing this change before.postNreleases work there.