ci(release): skip CI on the version-bump squash commit on main#3912
Merged
Conversation
Append `[skip ci]` to both the bump commit message and the release-PR title in `release.yml` and `release-sdk.yml`. The PR title doubles as the squash-merge commit message on `main`, so adding `[skip ci]` there is required to skip CI when the release PR is auto-merged into `main`. Affected flows: - release.yml -> chore(release): vX.Y.Z - release-sdk.yml -> chore(release): sdk-typescript vX.Y.Z These PRs only bump `package.json` / `package-lock.json` versions and do not need the full lint/test/CodeQL matrix to run on PR open, on the release branch push, or on the post-merge push to `main`.
wenshao
requested changes
May 7, 2026
Contributor
Code Coverage Summary
CLI Package - Full Text ReportCore Package - Full Text ReportFor detailed HTML reports, please see the 'coverage-reports-22.x-ubuntu-latest' artifact from the main CI run. |
wenshao
requested changes
May 7, 2026
Two follow-ups on the release-PR skip-ci change:
- Drop `[skip ci]` from the release-branch commit. Putting it there
also suppressed `push: tags: [v*]` workflows because the release
tag points at the release-branch tip, so `Build and Publish Docker
Image` would silently skip when the release was tagged. Keeping the
marker only on the squash subject preserves the "do not re-run CI
on main" goal without affecting tag pushes.
- Export `RELEASE_TAG` to the `Enable auto-merge for release PR` step
in both workflows. The step runs under `set -euo pipefail`, so the
new `--subject` referencing `${RELEASE_TAG}` would otherwise crash
with `unbound variable` and abort the merge.
wenshao
reviewed
May 7, 2026
wenshao
left a comment
Collaborator
There was a problem hiding this comment.
No review findings. Downgraded from Approve to Comment: no checks reported on the PR branch. — gpt-5.5 via Qwen Code /review
wenshao
approved these changes
May 7, 2026
wenshao
reviewed
May 7, 2026
wenshao
left a comment
Collaborator
There was a problem hiding this comment.
No review findings. All prior review comments have been resolved in this commit. LGTM!
— deepseek-v4-pro via Qwen Code /review
TaimoorSiddiquiOfficial
pushed a commit
to TaimoorSiddiquiOfficial/HopCode
that referenced
this pull request
May 8, 2026
…M#3912) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
DragonnZhang
pushed a commit
that referenced
this pull request
May 8, 2026
* ci(release): skip CI on auto-generated version-bump PRs
Append `[skip ci]` to both the bump commit message and the
release-PR title in `release.yml` and `release-sdk.yml`.
The PR title doubles as the squash-merge commit message on `main`,
so adding `[skip ci]` there is required to skip CI when the release
PR is auto-merged into `main`.
Affected flows:
- release.yml -> chore(release): vX.Y.Z
- release-sdk.yml -> chore(release): sdk-typescript vX.Y.Z
These PRs only bump `package.json` / `package-lock.json` versions
and do not need the full lint/test/CodeQL matrix to run on PR open,
on the release branch push, or on the post-merge push to `main`.
* ci(release): make skip-ci squash subject explicit
* ci(release): scope skip-ci to the squash commit and bind RELEASE_TAG
Two follow-ups on the release-PR skip-ci change:
- Drop `[skip ci]` from the release-branch commit. Putting it there
also suppressed `push: tags: [v*]` workflows because the release
tag points at the release-branch tip, so `Build and Publish Docker
Image` would silently skip when the release was tagged. Keeping the
marker only on the squash subject preserves the "do not re-run CI
on main" goal without affecting tag pushes.
- Export `RELEASE_TAG` to the `Enable auto-merge for release PR` step
in both workflows. The step runs under `set -euo pipefail`, so the
new `--subject` referencing `${RELEASE_TAG}` would otherwise crash
with `unbound variable` and abort the merge.
xaelistic
pushed a commit
to xaelistic/qwen-code
that referenced
this pull request
Jun 7, 2026
…M#3912) * ci(release): skip CI on auto-generated version-bump PRs Append `[skip ci]` to both the bump commit message and the release-PR title in `release.yml` and `release-sdk.yml`. The PR title doubles as the squash-merge commit message on `main`, so adding `[skip ci]` there is required to skip CI when the release PR is auto-merged into `main`. Affected flows: - release.yml -> chore(release): vX.Y.Z - release-sdk.yml -> chore(release): sdk-typescript vX.Y.Z These PRs only bump `package.json` / `package-lock.json` versions and do not need the full lint/test/CodeQL matrix to run on PR open, on the release branch push, or on the post-merge push to `main`. * ci(release): make skip-ci squash subject explicit * ci(release): scope skip-ci to the squash commit and bind RELEASE_TAG Two follow-ups on the release-PR skip-ci change: - Drop `[skip ci]` from the release-branch commit. Putting it there also suppressed `push: tags: [v*]` workflows because the release tag points at the release-branch tip, so `Build and Publish Docker Image` would silently skip when the release was tagged. Keeping the marker only on the squash subject preserves the "do not re-run CI on main" goal without affecting tag pushes. - Export `RELEASE_TAG` to the `Enable auto-merge for release PR` step in both workflows. The step runs under `set -euo pipefail`, so the new `--subject` referencing `${RELEASE_TAG}` would otherwise crash with `unbound variable` and abort the merge.
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
2 participants
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.
Summary
[skip ci]as the squash subject (viagh pr merge --subject) when the auto-generated release PR auto-merges intomain, so the squashed commit landing onmaindoes not re-run CI.package.json/package-lock.jsonversions but currently re-run the full check matrix on the post-mergemainpush, on top of the validation thatrelease.ymlalready runs (quality+integration_*jobs).release.ymlandrelease-sdk.ymlEnable auto-merge for release PRstep now explicitly passes--subject "...[skip ci]", instead of relying ongh pr merge's default of using the PR title.RELEASE_TAGin theirenv:block — without that,set -euo pipefailwould crash on${RELEASE_TAG}being unbound.[skip ci], sogh release create --target "${RELEASE_BRANCH}"does not silently suppress tag-push workflows likebuild-and-publish-image.yml.Behavior matrix (after this PR)
[skip ci])ci.yml+sdk-python.ymlrun once[skip ci])ci.yml+sdk-python.ymlrun oncegh release create --target ${RELEASE_BRANCH})build-and-publish-image.ymlruns as usualmain[skip ci]ci.yml,e2e.yml,sdk-python.ymlskipThe PR-time CI run is duplicative with
release.yml'squality/integration_*jobs but harmless, and stripping it would require job-levelif:filters inci.yml/sdk-python.yml— out of scope for this PR.Validation
maincarries[skip ci]andci.ymldoes not re-run onmain. The tag-push event still triggersbuild-and-publish-image.yml.Enable auto-mergeno longer fails onRELEASE_TAG: unbound variable.--subjectis passed inrelease.yml:457-461andrelease-sdk.yml:421-425.Enable auto-mergesteps exportRELEASE_TAGinenv:.release.yml:370andrelease-sdk.yml:324does not contain[skip ci].mainpush despite only changing version strings.Scope / Risk
mainlater adopts strict required status checks,[skip ci]on the squash commit would prevent those required checks from running andgh pr merge --autowould stall. Branch protection currently hasrequired_status_checks: null, verified before this change; revisit if that ever changes.Enable auto-mergestep is gated off in dry-run / nightly / preview paths, so the originalRELEASE_TAG: unbound variablecrash would only have manifested in a real production release.Testing Matrix
Workflow YAML change with no runtime / platform component — testing matrix not applicable.
Linked Issues / Bugs
None.