Repository navigation
Prepare Swift-JSON 1.0.0 release - #6
Merged
Merged
Conversation
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.
Prepare the first stable Swift-JSON release: promote the changelog to 1.0.0, use a semantic-version SwiftPM requirement, and update support/security/release guidance for the protected version tag and reviewed public assets.
Library sources, APIs, manifests, consumers, tests, finite profiles and benchmark workloads are unchanged. The existing streaming performance disposition is retained.
Validation: all required native, safety and DocC lanes must pass for this source, plus a clean extraction of the reproducible release archive through Scripts/ci.py --lane native. Source and compiled DocC snapshots, checksums and a public qualification receipt will accompany the release.