Repository navigation
ci: publish the built DAR as a release asset on tag push - #151
Merged
lmcorbalan merged 9 commits intoAug 31, 2026
Merged
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
Closes #145
There is no way to depend on this repository without cloning it and building, which drags the whole Splice vendoring flow downstream. This adds the workflow that publishes the built DAR as a release asset on a
v*tag push.Changes
.github/workflows/release.yml: asserts the pins, builds, proves the DAR byte-reproducible, runs the consumer smoke test, publishes with a generated body.workflow_dispatchruns every check and cannot publish, because the gate is the event, not an input.contents: writeis confined to this workflow, and the checkout does not persist its token.Acceptance criteria
Test plan
Automated tests
None; a workflow cannot be exercised until a tag exists.
Manual verification
Ran the workflow's step order locally:
npm test80 ok, DAR reproducible at147835e7, smoke green, tree clean. Extracted each step and ran it: the pin sweep names all three tracked manifests, and a manifest missing--target=2.1fails naming it. Aghshim confirmsv0.0.1-rc1publishes as a pre-release andv0.1.0does not.Breaking changes
None. Nothing runs until a
v*tag is pushed, and the rehearsal in #133 exercises the publish path on a throwaway tag first.Checklist
Screenshots
None.