Skip to content

chore: prepare OpenDomain 0.1.0-rc.1 - #20

Draft
chasechou007 wants to merge 1 commit into
mainfrom
codex/first-stable-rc1
Draft

chore: prepare OpenDomain 0.1.0-rc.1#20
chasechou007 wants to merge 1 commit into
mainfrom
codex/first-stable-rc1

Conversation

@chasechou007

Copy link
Copy Markdown
Contributor

Summary

  • prepare the exact 0.1.0-rc.1 compatibility candidate from the canonical source-first projection
  • move the forward release line to Apache-2.0 while preserving 0.1.0-alpha.10 and earlier as immutable MIT history
  • align package metadata, lockfile, changelog, public installation/usage guidance, and RC-aware validation assertions
  • use the explicit npm rc channel, which must not move latest

Compatibility 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

  • deterministic projection: 142 files / 744,547 bytes, inventory 1af1a00c3a3bbf10f5eb1054e88587ba7e48ad0f70d4e2c0891cf8b9387f005a
  • parity against main@44f0250: 126 identical / 16 reviewed intentional / 0 unexpected
  • Node 20 and Node 22: 226/226 tests, validate, installed-package smoke, Agent bootstrap
  • Node 24.18.0 standalone build/smoke
  • npm pack dry-run: 72 entries / 104,378 bytes; audit: 0 vulnerabilities / 39 dependencies
  • real corpus compatibility: Zimi PDM 32 docs, KeptNear 22 docs, EchoPath 8 docs; zero errors/warnings

Approval boundary

This Draft PR is remote-integration evidence only. It does not authorize Ready-for-review, merge, main update, tag creation, npm publication or dist-tag changes, GitHub Release/standalone asset publication, branch-protection changes, repository lifecycle changes, or OpenSpec archive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant