chore: prepare OpenDomain 0.1.0-rc.1 - #20
Draft
chasechou007 wants to merge 1 commit into
Draft
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
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.
Summary
0.1.0-rc.1compatibility candidate from the canonical source-first projection0.1.0-alpha.10and earlier as immutable MIT historyrcchannel, which must not movelatestCompatibility surface
This RC rehearses the intended first-stable surface: published Markdown/YAML schemas, Grounding Protocol v1, Core API 1.0,
opendomain.context-export.v1, existing CLI/exit semantics, workspace resolution, and package-neutral npm/standalone behavior.Validation
1af1a00c3a3bbf10f5eb1054e88587ba7e48ad0f70d4e2c0891cf8b9387f005amain@44f0250: 126 identical / 16 reviewed intentional / 0 unexpectedApproval boundary
This Draft PR is remote-integration evidence only. It does not authorize Ready-for-review, merge,
mainupdate, tag creation, npm publication or dist-tag changes, GitHub Release/standalone asset publication, branch-protection changes, repository lifecycle changes, or OpenSpec archive.