build: use the latest TinyGo release container instead of the dev container for builds - #826
Merged
Conversation
deadprogram
force-pushed
the
pin-to-release
branch
2 times, most recently
from
December 15, 2025 17:55
3f4f9cd to
5f9c88e
Compare
…tainer for builds. Signed-off-by: deadprogram <ron@hybridgroup.com>
deadprogram
force-pushed
the
pin-to-release
branch
from
December 15, 2025 18:02
5f9c88e to
c6a4c62
Compare
ysoldak
approved these changes
Dec 15, 2025
Member
Author
|
Thanks for review @ysoldak now merging. |
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.
This PR is to use the latest TinyGo release container instead of the dev container for builds, as discussed by the team.