Repository navigation
Release @shivaedev/admin 0.26.0 and 19 more packages - #2296
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release/next
branch
5 times, most recently
from
November 18, 2026 05:52
6a2cd8a to
951f5cf
Compare
github-actions
Bot
force-pushed
the
release/next
branch
2 times, most recently
from
November 18, 2026 06:08
c8e53d0 to
e2315bb
Compare
github-actions
Bot
force-pushed
the
release/next
branch
3 times, most recently
from
November 18, 2026 06:36
30377be to
67ca245
Compare
github-actions
Bot
force-pushed
the
release/next
branch
from
November 18, 2026 06:37
67ca245 to
aceac61
Compare
marvin-bitterlich
enabled auto-merge
November 18, 2026 12:47
Coverage 91.9% (−0.1 pts)No coverable lines added.
|
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.
Why?
This PR holds the current release plan: press Approve and run, then merge when full CI is green.
How?
This branch is regenerated from main with the releases plan applied. Merging it builds and publishes this frozen branch commit through the main-only npm trusted publishing workflow. Later changesets stay pending while this release still passes release validation against main. A conflict or invalid release plan regenerates this PR and requires a new CI approval. Release notes and tags target this branch head; npm provenance records the pushed main commit that runs the workflow, with GitHub’s OIDC environment unchanged.
Migration steps and change notes are in each package's
CHANGELOG.mdin this diff and lead the GitHub release.Decisions