Release 1.0.0 - #4
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.
Sync of
1.0.0from the workspace.1.0.0 freezes the public API. Field names, status codes, the objective vector, the
numeric policy and the validation rules do not change without a major version, so any
1.xis a safe upgrade from any earlier1.x.docs/GUARANTEES.mdandSECURITY.mdare updated accordingly — the previous text said the API was not frozen, which this
release makes false, and
SECURITY.mdstill named0.1.xas the supported line.What 1.0.0 does not claim
Exercised on Linux x86_64, Linux aarch64 and macOS arm64 only. No build-provenance
attestation exists for this release and
gh attestation verifycannot succeed againstit. Windows is not built.