chore: add action to update fuelup versions and deploy - #121
Open
JoshuaBatty wants to merge 3 commits into
Open
Conversation
kayagokalp
previously approved these changes
Jun 26, 2025
kayagokalp
approved these changes
Jun 26, 2025
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
2 participants
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.
Description
This PR introduces a manual GitHub Actions workflow to simplify updating the fuelup toolchains and deploying the application.
Previously, updating the forc version in the production environment was difficult due to Docker layer caching in the CI pipeline. A rebuild was only triggered on a file change.
The new "Manual Deploy" action can be triggered on-demand from the Actions tab. It includes an option to bypass the Docker cache, which forces a fresh build and ensures the latest toolchain versions are installed from fuelup.