chore(manifest): post-cut bookkeeping for v0.7.0 #109
No reviewers
Labels
No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit!109
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "release-toolkit/manifest-v0.7.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automated manifest update for v0.7.0 release cut.
Why this PR? The release-toolkit cut path opens a PR for the manifest update rather than direct-pushing to
mainso the toolkit remains compatible with branch protection rules without requiring consumers to provision admin-scope tokens. See release-toolkit#78 for the substrate-honest rationale.Expected lifecycle: CI runs against this PR; the workflow attempts auto-merge via the Forgejo API; if auto-merge succeeds the next workflow run detects
mode=noop(manifest matches HEAD) and exits clean.If this PR sits open: branch protection forbids the workflow token from auto-merging. Either merge manually (one-off action), or wire a separate auto-merge mechanism for PRs from
release-toolkit/manifest-*branches. Until the manifest update lands,release-decide.shwill not advance its walk window.