Refresh fork from changesets action v1.9.0 - #22
Open
freben wants to merge 3 commits into
Open
Conversation
This was referenced Sep 4, 2026
Signed-off-by: Fredrik Adelöw <freben@gmail.com> Co-Authored-By: Codex <noreply@openai.com>
freben
force-pushed
the
freben/refresh-v1.9.0
branch
from
September 4, 2026 09:58
796f06f to
0f2ad4f
Compare
Signed-off-by: Fredrik Adelöw <freben@spotify.com>
Signed-off-by: Fredrik Adelöw <freben@spotify.com>
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.
Refreshes the ancient fork baseline to upstream
changesets/actionv1.9.0 while retaining only theversionBranchinput required bybackstage/community-plugins. Removes fork-specific automatic release workflows and documents thatbackstage/backstageuses the official action directly.Release preparation
distis already current onmain.v3.0.0tag and movingv3branch atomically, with force scoped only to the moving branch.After this PR is merged, v3.0.0 can be published by following the new Releasing this fork section in the README. Merging alone does not publish the release or update
backstage/community-plugins.Verification
pnpm formatpnpm typecheckpnpm exec vitest --run --testTimeout=30000(14 tests)pnpm buildgit diff --check30b512d) using a nested Changesets workspace, customversionBranch, legacyGITHUB_TOKENenvironment input, workspace-scoped file verification, generated PR-body verification, and generated-commit DCO verification.