Repository navigation
Drop the toolchain notes from the Button page - #4
Merged
Merged
Conversation
1.2.0 shipped in April 2025 and anyone starting now is on 1.2.x or 1.3.x, so the warning spent its space on a case that no longer comes up. The version floor itself still holds and is recorded in the registry's README, next to the source it constrains.
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Same reasoning: MainActor isolation is the Xcode 26 default, so the component's nonisolated override is simply correct and the mistake the note guarded against cannot be reached from the source on the page.
zumkorn
changed the title
This branch was successfully deployed
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
1 participant
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.
Both notes described environments that no longer come up:
nonisolated— MainActor isolation is the Xcode 26 default, so the component's override is simply correct; the mistake the note guarded against cannot be reached from the source shown on the page.The version floor itself still holds and stays recorded in the registry README, next to the source it constrains.