Repository navigation
fix(ci): gate wallet builds and deployment on published releases - #613
Open
harshgupta6789 wants to merge 1 commit into
Open
harshgupta6789 wants to merge 1 commit into
harshgupta6789 wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The workflows currently build and push a Docker image even when semantic-release determines that no release is needed.
This change separates release, build, and deployment into dependent jobs. Builds require
new-release-published == 'true', and development deployment and post-deploy tests also require their preceding jobs to succeed.Release outputs are exported through
@semantic-release/exec. Downstream jobs check out the release tag and use the released version as the Docker image tag. The release job fetches full Git history and uses Node.js LTS.The same check is added to the v1.10 patch workflow. Run it from
master; it still releasesv1.10. The README has been updated with these instructions.Validation: 11 local release scenarios passed, covering release, no-release, and failure paths. Workflow checks passed with existing deprecated-action warnings excluded. The workflows still need verification in GitHub Actions.
Related to Greenstand/treetracker-infrastructure#330. This PR covers treetracker-wallet-api only.