Skip to content

fix(ci): never supersede release-relevant CI runs so release PRs stay green - #40

Merged
Shinrai merged 1 commit into
nextfrom
ci/release-pr-always-green
Aug 4, 2026
Merged

fix(ci): never supersede release-relevant CI runs so release PRs stay green#40
Shinrai merged 1 commit into
nextfrom
ci/release-pr-always-green

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

@cldmv-bot cldmv-bot Bot added ! ci → next v4 flow: ci contributor PR targeting the next integration branch type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files labels Aug 4, 2026
…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 force-pushed the ci/release-pr-always-green branch from 828a2cb to c58633f Compare August 4, 2026 04:46
@Shinrai
Shinrai merged commit f4735a4 into next Aug 4, 2026
12 checks passed
@cldmv-bot
cldmv-bot Bot deleted the ci/release-pr-always-green branch August 4, 2026 04:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

! ci → next v4 flow: ci contributor PR targeting the next integration branch type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant