feat: add postrelease version
#1816
Open
+731
−187
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.
Description
postreleaseflagdevreleaseand added new docs forpostreleaseTODOon lack of support forpostreleaseprerelease_propertytests as well as thepostrelease_propertyonesChecklist
Code Changes
uv run poe alllocally to ensure this change passes linter check and testsDocumentation Changes
uv run poe doclocally to ensure the documentation pages renders correctlyExpected Behavior
when using the new
postreleaseflag, apostNwill be added beforedevNSteps to Test This Pull Request
Additional Context
over the last couple of years, professionally, our internal workflows have been using
commitizen,in an older version fork, where we internally added support for a couple of missing features at the time, one waspostrelease.