Repository navigation
chore: prepare shared packages and release setup for 0.0.3 - #8
Merged
anilkreddy merged 4 commits intoNov 14, 2026
Merged
Conversation
…imitives-0.0.3 # Conflicts: # packages/ccv2-client/CHANGELOG.md
anilkreddy
changed the title
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.
Prepare both packages at exact version 0.0.3 on the preview channel, stacked on implementation #7. Merge #7 first, then retarget this PR to main and review the version/release documentation change.
The consumer audit found all required APIs present: notification schema/context/event factories for Notify, Build and Deploy; shared technical-user auth and policy-driven HTTP transport for Build/Deploy; and the new path encoder plus opt-in markup/JWT text primitives. Build/Deploy retain their existing sanitization order and malformed-Unicode error classification. NotificationEvent schemaVersion remains 1. Consumer-specific rendering, lifecycle, endpoint validation and delivery retries stay in their owning repositories.
Document future release configuration in docs/github-packages.md: automatic GITHUB_TOKEN permissions, package visibility/association, consumer Actions access, registry setup and local read credentials. Link the configuration from RELEASING.md and README, update dispatch examples to 0.0.3, and reconcile the extraction audit with the prepared versions.
Validation for the updated head: full pnpm quality (264 tests; 100% line coverage; package builds; packed ESM/schema/declaration/export checks; public scan; dependency audit) and git diff --check passed locally. Source and consumer audits found no additional required runtime exports. Registry inspection confirmed both packages currently publish only 0.0.1 and 0.0.2.
Publication is still pending: the main-only owner workflow requires these changes merged and exact-main CI/CodeQL green, then separate preview publication for each package. No tags/releases or publication were performed. Notify/Build/Deploy source migrations are prepared locally, but genuine 0.0.3 registry installs, regenerated lockfiles/bundles and full consumer quality gates must follow publication before those migration branches are pushed. Package publication does not release the Actions or satisfy their coordinated Sandbox/provider release gates.