feat(cmd-version): enable version stamp of vars with double-equals operand in version_variables
#1244
Conversation
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
…file with double-equals
… double-equals (`==`)
…uble-equals operand support
574355d to
6950741
Compare
🎉 This PR has been published as part of v10.0.0 🎉You can find more information about this release on the GitHub Releases page. |
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.
Purpose
==.Rationale
Needed to add a feature in order to stamp into
requirements.txtfor when PSR will update its Github Action dependencies definition which I needed to be in thepip freezeformat ofrequirements.txt.How did you test?
Added a unit test to verify that a version definition with
==will be updated with a new version.PR Completion Checklist
Reviewed & followed the Contributor Guidelines
Changes Implemented & Validation pipeline succeeds
Commits follow the Conventional Commits standard
and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs)
Appropriate Unit tests added/updated
N/A
Appropriate End-to-End tests added/updatedAppropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)