Add guarded Core release publication and GitHub workflow - #1
Merged
Merged
Conversation
dillonlille
marked this pull request as ready for review
September 12, 2026 03:49
dillonlille
marked this pull request as draft
September 12, 2026 03:57
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.
Core now has a manually triggered release workflow that packages a verified main commit with the owner-selected version and reviewed notes. It verifies build provenance and uploaded assets, rejects existing versions and changed component bytes under an existing version, and publishes without activating production.
The SDK owns the shared publication tooling used by both repositories and supports bounded per-repository test concurrency. Core releases also carry the platform dependency bundle for DSP builds. The workflow checks main and its successful push checks again before publication, creates a draft, verifies uploaded assets, and only then publishes. Failures preserve the draft for inspection.
Validation: 75 Core tests pass, including seven publication tests covering deterministic packaging, tampering, main/check identity, duplicate versions, component version reuse, and upload failure recovery. Source checks and the dashboard build pass. Actionlint validates workflow syntax locally and in CI; the public source export scan has no findings. Full Core and DSP development artifacts were packaged and verified locally with synthetic publication metadata.
GitHub checks passed for
90e29d2940eac250b15042e336661562cff72fe1. Actual release upload/attestation publication remains unexercised because no release has been requested. This PR does not change production, deploy the permanent Dev DSP, or wire the owner update buttons.Merge requires the owner’s explicit chat approval. Publishing and installation remain separate steps.