Repository navigation
Merge v4-beta to v4 (2026-10-27) - #227
Merged
Merged
Conversation
…PR is labelled mark-unstable
build-ready, build-failed, publish and tests pasted the raw head commit message into a JSON string. A message with quotes, braces or backticks (a squashed PR body) broke the payload: slack-github-action failed with 'missed comma between flow collection entries', and in docker-ecr-argocd that failed build-app and skipped the ArgoCD values update (mistat2 #5). The message now goes through nunjucks 'dump' (JSON.stringify) and is cut to 2900 characters, under Slack's 3000-character limit for a text field.
node-simple-pnpm: publish without the stable channel when the merged PR is labelled mark-unstable
mike-ainsel
approved these changes
Oct 29, 2026
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.
Merge v4-beta into v4. The only change is #225: a block PR labelled
mark-unstablepublishes the block without adding it to the stable channel. PRs without the label release as before.What changes on v4
node-simple-pnpm.yaml, jobbuild-test-publish:GITHUB_SHA. If it hasmark-unstable, the "Auto-generated changes" commit gets aPublish-Unstable: truetrailer.PL_PUBLISH_UNSTABLE=trueand adds an "Unstable release" notice to the run.block-tools publishreads that variable as--unstable.If the PR lookup fails, the version commit is not pushed and nothing is published. Repos that don't publish blocks are unaffected apart from one extra API call on runs that push a version commit.
Canary
Ran on platforma-open/xsv-import#9 with the workflow pinned to the feature branch:
8faa7f3carriesPublish-Unstable: true.channels: [], and stable is still 2.0.1.Registry check (anyone can re-run it):
Publish jobs:
The commit→PR lookup was also checked against 6 merge-queue merges in 3 repos; all 6 found their PR.
Not covered
max_entries_to_merge: 5). Only the last PR in such a batch is checked.In either case,
block-tools mark-stable --unmarktakes the released version back out of the stable channel.Rollout
The
mark-unstablelabel exists in 77 of 78 block repos.import-bulk-count-matrixstill needs it, from someone with write access.