Skip to content

chore: Add concurrency control to npm-publish workflow#58

Open
1234-ad wants to merge 1 commit into
accordproject:mainfrom
1234-ad:chore/add-concurrency-control
Open

chore: Add concurrency control to npm-publish workflow#58
1234-ad wants to merge 1 commit into
accordproject:mainfrom
1234-ad:chore/add-concurrency-control

Conversation

@1234-ad
Copy link
Copy Markdown

@1234-ad 1234-ad commented Jan 12, 2026

Summary

This PR adds concurrency control to the npm-publish workflow to prevent duplicate workflow runs for the same release.

Changes

  • Added concurrency group based on release tag name
  • Enabled cancel-in-progress to stop duplicate runs
  • Improves CI/CD efficiency and prevents race conditions

Related Issue

Fixes #56

Testing

  • Workflow configuration validated
  • Concurrency settings follow GitHub Actions best practices

- Add concurrency group to prevent duplicate workflow runs
- Cancel in-progress runs when new release is created
- Improves CI/CD efficiency and prevents race conditions

Fixes accordproject#56
@mttrbrts
Copy link
Copy Markdown
Member

Thanks for this contribution! Before we can merge, all commits need to be signed off for the Developer Certificate of Origin.

Please run:

git rebase HEAD~N --signoff  # where N = number of commits
git push --force-with-lease

See CONTRIBUTING.md for details.


This comment was generated by AI on behalf of @mttrbrts.

@github-actions github-actions Bot added the maintainer-engaged A maintainer has commented or reviewed this item label May 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintainer-engaged A maintainer has commented or reviewed this item

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore: Add concurrency control to npm-publish workflow

2 participants