[trueberryless]

🧭 Context

Fix red CI on main.

📚 Description

This PR fixes the failing (canceled) enforce-release-source.yml check, which happens on main because multiple runs are triggered simultaneously there by removing the concurrency block entirely. This also means adding a zizmor ignore rule for this action only, but I think it is the best solution .

🔗 Related resources

• We tried setting cancel-in-progress to false (by removing it): fb6916b
• We had the synchronize trigger removed for a while: ci: remove edited type trigger from enforce-release-source #2896 (sorry for the confusing PR title), but since the ruleset makes it a necessary status check, the release PR is always blocked after a new commit lands on main. This is why @danielroe added it again: af01d90

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
npmx.dev	Ready	Preview	Oct 30, 2026 8:42pm UTC

2 Skipped Deployments

Project	Deployment	Actions	Updated
docs.npmx.dev	Ignored	Preview	Oct 30, 2026 8:42pm UTC
npmx-lunaria	Ignored		Oct 30, 2026 8:42pm UTC

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: npmx-dev/npmx.dev
• Branch: main
• File: .coderabbit.yaml
• Commit: 5477c91
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 65141948-45d6-48f0-a04d-2cc93eee99de

Commits

Reviewing files that changed from the base of the PR and between 5477c91 and e633062.

Files selected for processing: 2

• .github/workflows/enforce-release-source.yml
• .github/zizmor.yml

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated release-check automation settings. The check continues to run for pull requests with the same permissions and source validation.
  • Concurrency grouping is no longer configured for this check, and its concurrency-limit exception is documented.
  • These changes affect the project’s automation only; no changes to user-facing features or product behaviour are included.

The release-source workflow no longer sets concurrency options. The zizmor configuration now excludes this workflow from concurrency-limit checks and documents the stated concurrency behaviour.

Changes: Release-source workflow concurrency

Layer / File(s)	Summary
Update release-source concurrency policy .github/workflows/enforce-release-source.yml, .github/zizmor.yml	The workflow no longer defines a concurrency group or sets cancel-in-progress. The zizmor configuration excludes this workflow from concurrency-limits and documents the stated concurrency behaviour.

Suggested reviewers: alexdln, danielroe

Merge Risk: Minimal · up to e6330

The change removes concurrency restrictions from the release-source check without changing its validation logic. No actionable merge-blocking risk is identified; merge after normal checks pass.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title names the main change: the workflow no longer cancels the target branch check. The raw summary confirms the concurrency block was removed from enforce-release-source.yml, which matches the t…
Description check		The description states the purpose: fixing the canceled enforce-release-source.yml check on main. It explains removing the concurrency block and adding a zizmor ignore rule. The related-resources link…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title names the main change: the workflow no longer cancels the target branch check. The raw summary confirms the concurrency block was removed from enforce-release-source.yml, which matches the title's intent. The title uses the 'ci:' prefix and stays under 70 characters. It does not describe the zizmor ignore rule, but that is a secondary change.

Full details: Description check

Explanation

The description states the purpose: fixing the canceled enforce-release-source.yml check on main. It explains removing the concurrency block and adding a zizmor ignore rule. The related-resources links cover earlier attempts, such as setting cancel-in-progress to false and restoring the synchronize trigger. All of this matches the changeset.

Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!