Repository navigation
fix(templates): use published Proton 0.9.1 - #537
Merged
Merged
Conversation
Milky2018
marked this pull request as ready for review
November 17, 2026 12:12
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.
New applications created by
proton_cli 0.9.1 newstill depend on Proton 0.8.0 because the wrapper fetches templates from main. On the current MoonBit toolchain, their transitive xlog 0.4.2 fails to compile. The 0.9.1 release workflow successfully published all 24 packages, then failed the independent acceptance check at the first compile of the unmodified scaffold, before its dependency-upgrade step.Update both templates' Proton dependencies and their CLI version instructions to the now-published 0.9.1. Retain the existing async 0.22.7 compatibility bridge for standalone async dependencies. No runtime code, package versions, or acceptance assertions change.
Validated locally on macOS with an isolated latest toolchain (
moonc 0.10.21+06da1ed44):moon fmt --check, andgit diff --checkpassed.Full platform CI is pending. After merging, only the failed registry-acceptance job of the original release run needs rerunning. The published 0.9.1 packages must not be published again.