Skip to content

Fix Beta 2 registry consumer type verification - #59

Merged
douglas-grishen merged 1 commit into
mainfrom
codex/beta2-release-evidence
Aug 1, 2026
Merged

Fix Beta 2 registry consumer type verification#59
douglas-grishen merged 1 commit into
mainfrom
codex/beta2-release-evidence

Conversation

@douglas-grishen

Copy link
Copy Markdown
Contributor

What changed

  • replace two stale, non-exported Beta 2 consumer type names with the actual public contracts
  • keep the release consumer checking the same action-guard and governed Mesh integration surfaces

Root cause

The release fixture referenced provisional type names that were renamed before the packages were frozen. Package publication completed, but the clean pnpm consumer failed during TypeScript verification.

Impact

The release workflow can now validate the already-published immutable 0.3.0-beta.2 packages without changing package contents or registry artifacts.

Validation

  • 17/17 focused publisher and registry-consumer tests
  • clean pnpm portable registry consumer: 36 packages, 58 export subpaths
  • clean npm portable registry consumer: 36 packages, 58 export subpaths
  • clean pnpm PostgreSQL registry consumer: 14/14 control conformance cases
  • Prettier and git diff --check

@douglas-grishen
douglas-grishen marked this pull request as ready for review August 1, 2026 16:04
@douglas-grishen
douglas-grishen merged commit 68be971 into main Aug 1, 2026
2 checks passed
@douglas-grishen
douglas-grishen deleted the codex/beta2-release-evidence branch August 1, 2026 16:05
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