add an auto-deploy action for stable releases #1565
Merged
Conversation
This file contains 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
.github/workflows/publish-stable.yml
Outdated
| # This will only cause the `check-plan` job to have a result of `success` | ||
| # when the .release-plan.json file was changed on the last commit. This | ||
| # plus the fact that this action only runs on main will be enough of a guard | ||
| - run: git diff --name-only HEAD HEAD~1 | grep -w -q ".release-plan.json" |
NullVoxPopuli
approved these changes
Jul 31, 2023
mansona
force-pushed
the
auto-release
branch
2 times, most recently
from
7c35c4e to
732070f
Compare
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.
This is starting the conversation about auto-release again which was temporarily paused in #1492 to make the PR easier to get merged.
I assume this will start a large conversation but for now it's a pretty simple process: if the
.release-plan.jsonwas touched in the last commit to main then use the release script to push that to npm 👍