chore(conf): configure project to stamp ci action's requirements.txt w/ new version
#1248
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
…xt w/ new version
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
With the refactor of the GitHub action Docker build, I changed it to actually download the published python-semantic-release package rather than just load the GitHub source code into the container. This ensures that we have less disparity between what users report errors as the runtimes are different. We must now bump the version value in the
requirements.txtthat is used when building the GitHub Action when we bump the overall version.How did you test?
Manually with the stamp only command to make sure the newly defined version is inserted into
src/gh_action/requirements.txtPR 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)
N/A
Appropriate Unit tests added/updatedN/A
Appropriate End-to-End tests added/updatedN/A
Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)