Repository navigation
fix(ci): skip image build and tag update when no release - #92
Draft
kruchkovnik15-dot wants to merge 2 commits into
Draft
kruchkovnik15-dot wants to merge 2 commits into
kruchkovnik15-dot wants to merge 2 commits 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 workflow currently builds and pushes a Docker image and updates the development image tag even when semantic-release determines that no new release is needed.
This change exports release outputs through @semantic-release/exec and runs the image build and development tag update only when new-release-published is true. The image tag uses the version reported by semantic-release.
The release job fetches full Git history, uses Node.js LTS, and declares the required GitHub token permissions. The development update commits staged deployment changes only when there is a diff.
Validation: the workflow has not been executed. Dependency compatibility with Node.js LTS and both release/no-release paths still need validation.
Related to Greenstand/treetracker-infrastructure#330. This PR covers treetracker-messaging-api only.