Repository navigation
chore: bump foundry-cli to 0.0.50 - #38
Merged
Merged
Conversation
anandpant
marked this pull request as ready for review
October 5, 2026 03:51
Contributor
Author
Merge activity
|
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
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.

Foundry-only release index update
Release follow-through for foundry-cli #782 and stable v0.0.50.
Only
foundry-cli-bin/PKGBUILDand.SRCINFOchange. These two generated files are copied byte-exact from automation PR #37 at53a3500655be15cf0b09f00eda61fbe92cff82c1; its unrelated Tabex/Meshix changes are deliberately left untouched and are not included here.The release Linux archive SHA256 is
c741c6a597488a38253272a156a8c8a241ffaeee9de9e3dc92fd2d8bed2bd57b, independently downloaded and matched against both the published checksums and release asset digest. Local PKGBUILD shell syntax and the maintained release-archive validator passed. No user package installation, stable binary upgrade, account/keychain change, or Foundry/model call.Current-head hosted validation must execute before merge. The mixed bot PR's prior action-required/zero-job run is not validation proof and is not reused for this PR.