feat(release): add dry-run validation pipeline - #38
Merged
osnoser1 merged 2 commits intoJun 8, 2026
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Copy link
Copy Markdown
✅ Deploy Preview for limitless-angular-sanity-example canceled.
|
Sorry, something went wrong.
osnoser1
marked this pull request as ready for review
June 8, 2026 02:01
osnoser1
force-pushed
the
osnoser1/release-dry-run-validation
branch
from
6501a3f to
32e2cc6
Compare
June 8, 2026 02:05
Copy link
Copy Markdown
npm i https://pkg.pr.new/@limitless-angular/sanity@38 commit: 5148566 |
Sorry, something went wrong.
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.
PR Checklist
Closes #28
What is the new behavior?
Adds @limitless-angular/release-tools as the canonical release orchestrator. The package plans releases, applies the prospective version/changelog in the runner workspace, validates the packed compatibility artifact, and only then runs publish side effects.
The release workflow is now publish-only, and a dedicated Release Dry Run workflow validates the same prospective artifact without npm credentials or publish side effects.
Does this PR introduce a breaking change?
Other information
Validation performed locally:
Post-Deploy Monitoring & Validation
No additional runtime monitoring required because this changes repository release automation, not application runtime behavior.
After merge, validate the next manual Release Dry Run workflow run succeeds before using Release and Publish. Healthy signal: dry-run completes release:dry-run, compat:pack, compat:artifact, and compat:test with the planned artifact version. Failure signal: any release dry-run workflow failure or artifact version mismatch; mitigation is to keep using the existing npm package version and block manual publish until the workflow failure is fixed.