chore: pin CI workflows to v4 and publish block as stable - #44
Merged
Conversation
- switch context/init and node-simple-pnpm.yaml from the MILAB-6707_changeset-coverage-gate branch to @v4 - drop --unstable from the block prepublishOnly step - normalize quoting in build.yaml
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.
Changes
.github/workflows/build.yaml: switchactions/context/initandnode-simple-pnpm.yamlfrom the temporaryMILAB-6707_changeset-coverage-gatebranch to the released@v4block/package.json: drop--unstablefromprepublishOnly, so the block is published as a stable releasebuild.yamlChangeset
An empty changeset is included — no version bump for the published
blockpackage is intended, this only affects CI configuration and publish flags.Greptile Summary
This PR moves CI references from a temporary feature branch to the released
v4line and changes the block publication command from unstable to stable. It deliberately includes an empty changeset, so no package version is bumped.context/initandnode-simple-pnpm.yamlnow resolve through@v4instead of@MILAB-6707_changeset-coverage-gate.prepublishOnlyno longer passes--unstabletoblock-tools publish.require-package-path-bump: true.Confidence Score: 5/5
The PR appears safe to merge because no concrete, changed-code-triggered failure was established.
The workflow references remain consistent with the repository’s existing
v4convention, while the possible reusable-workflow input mismatch and stable republishing collision depend on external contract or registry facts not established by the available evidence.Important Files Changed
@v4and normalizes YAML quoting; no locally verifiable workflow-contract defect was established.--unstablefromprepublishOnly, making subsequent block publication stable; no concrete collision or overwrite behavior was established.Reviews (1): Last reviewed commit: "chore: pin CI workflows to v4 and publis..." | Re-trigger Greptile