Skip to content

release: v1.3.8 - never supersede release-relevant CI runs so release… - #20

Merged
Shinrai merged 5 commits into
masterfrom
next
Aug 4, 2026
Merged

release: v1.3.8 - never supersede release-relevant CI runs so release…#20
Shinrai merged 5 commits into
masterfrom
next

Conversation

@cldmv-bot

@cldmv-bot cldmv-bot Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

🚀 What's Changed

💥 Breaking Changes

No breaking changes

✨ Features

No new features

🐛 Bug Fixes

📦 Dependencies

No dependency updates

🔧 Other Changes

No other changes

👥 Contributors

coverage

Metric Coverage
Statements 100.0%
Branches 100.0%
Functions 100.0%
Lines 100.0%

Avg: 100.0% · 77a97f8 · Node lts/*

Shinrai and others added 3 commits August 3, 2026 20:39
… green

Give pushes to master/main/next/hotfixes and the next/hotfixes → master/main
release PRs a UNIQUE concurrency group per run (run_id appended) instead of a
per-ref group with cancel-in-progress. During the burst of pushes a release
makes to next/hotfixes (the feature squash, the post-hotfix master→next sync
merge, the bot's `chore: bump version`), the earlier run was cancelled into a
red X on the release PR; each now runs to completion and posts a green check.

Feature branches / feature PRs keep cancel-in-progress. A bare
`cancel-in-progress: false` wouldn't suffice — GitHub still cancels the middle
PENDING run when a newer one queues; a unique-per-run group avoids all of it.

Mirrors the CLDMV/.github core-cicd `ci.yml` template change.
@cldmv-bot cldmv-bot Bot added ! release → master v4 flow: persistent next → master release PR (carries the next feature release) release Marks a pull request as a pending release — merge to publish a new version semver: patch This release contains only backwards-compatible bug fixes type: bug Something is broken or not behaving as expected type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files type: dependencies Relates to dependency updates, version bumps, or package management labels Aug 4, 2026
@cldmv-bot

cldmv-bot Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor Author

🔒 Dependency Review

  • 0 vulnerable package(s)
  • 0 package(s) with incompatible licenses
  • 0 package(s) with invalid SPDX license definitions
  • 0 package(s) with unknown licenses
  • 0 denied package(s)
  • 0 package(s) with OpenSSF Scorecard score < 3

Full job summary

Shinrai and others added 2 commits August 3, 2026 21:43
…coded master/main)

The concurrency group must never supersede release-relevant runs so the release
PR posts a green check. The base branch is now DERIVED the same way
resolve-release-base does — the CLDMV_RELEASE_BASE var, else the repo's
default_branch — instead of the hardcoded refs/heads/master || refs/heads/main.
next/hotfixes stay literal (the flow's fixed integration branches) and the
release-PR detection (github.head_ref == next/hotfixes) was already base-agnostic.

Mirrors the CLDMV/.github core-cicd ci.yml template.
@Shinrai
Shinrai merged commit 495b360 into master Aug 4, 2026
24 checks passed
@cldmv-bot
cldmv-bot Bot deleted the next branch August 4, 2026 05:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

! release → master v4 flow: persistent next → master release PR (carries the next feature release) release Marks a pull request as a pending release — merge to publish a new version semver: patch This release contains only backwards-compatible bug fixes type: bug Something is broken or not behaving as expected type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files type: dependencies Relates to dependency updates, version bumps, or package management

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant