👷 Add automated frontend release process workflow #119
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
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @mingi3314 and the rest of your teammates on |
Merge activity
|
mingi3314
deleted the
04-15-_add_automated_frontend_release_process_workflow
branch
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.
TL;DR
This PR adds an automated release process for the frontend code.
What changed?
A new Github Action workflow file
frontend-release.yamlhas been added. This workflow triggers on a push to themainbranch with changes in thefrontend/directory. It compares the current version inpackage.jsonwith the latest release tagged on Github. If the version has changed, it creates a new release.How to test?
To test, make a change in the frontend directory that updates the version in
package.json, then push tomain. Check the 'Actions' tab on Github to see the workflow run and the 'Releases' tab to see the new release.Why make this change?
This change automates the release process, reducing the likelihood of human error and simplifying the release process for new changes.