Skip to content

release: v0.0.4 - derive release base in never-supersede concurrency… - #13

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

release: v0.0.4 - derive release base in never-supersede concurrency…#13
Shinrai merged 3 commits into
masterfrom
next

Conversation

@cldmv-bot

@cldmv-botcldmv-botBot commented Aug 4, 2026•
edited
Loading

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

MetricCoverage
Statements100.0%
Branches100.0%
Functions100.0%
Lines100.0%

Avg: 100.0% · 156ba07 · Node lts/*

Shinraiand others added 3 commits August 3, 2026 21:43
@Shinrai
fix(ci): derive release base in never-supersede concurrency (not hard…
21ee07b
…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
fix(ci): never supersede release-relevant CI runs so release PRs stay…
3cf1ec8
… green (#12)
@cldmv-bot
chore: bump version to 0.0.4
7fe98f9
@cldmv-botcldmv-botBot 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-botBot commented Aug 4, 2026

Copy link
Copy Markdown
ContributorAuthor

🔒 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
Shinrai merged commit eb0cf89 into masterAug 4, 2026
26 checks passed
@cldmv-bot
cldmv-botBot deleted the next branch August 4, 2026 05:15
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ShinraiShinraiShinrai approved these changes

Assignees

No one assigned

Labels

! release → masterv4 flow: persistent next → master release PR (carries the next feature release)releaseMarks a pull request as a pending release — merge to publish a new versionsemver: patchThis release contains only backwards-compatible bug fixestype: bugSomething is broken or not behaving as expectedtype: ciChanges to CI workflows, actions, or build pipelinestype: configChanges to repository or project configuration filestype: dependenciesRelates to dependency updates, version bumps, or package management

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Shinrai