Update workflows

[danielsitek]

This pull request updates the GitHub Actions workflows to improve reliability, efficiency, and concurrency handling. The main changes include adding concurrency controls, updating action versions, and enhancing caching and release steps.

Workflow concurrency and efficiency improvements:

• Added concurrency groups to both .github/workflows/dev.yml and .github/workflows/release.yml to prevent overlapping workflow runs; in development, in-progress runs are cancelled, while in release, they are not. [1] [2]
• Enabled npm caching in the Node.js setup step of the development workflow to speed up dependency installation.

Action version updates and enhancements:

• Updated actions/checkout and actions/setup-node to their latest minor/patch versions (v6.0.1 and v6.1.0) in both workflows for improved stability and bug fixes. Also set fetch-depth: 0 in the release workflow to ensure full git history is available. [1] [2]
• Updated softprops/action-gh-release to v2.5.0 in the release workflow and explicitly set draft: false and prerelease: false to ensure published releases are final and not drafts or prereleases.

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow configurations to improve build reliability and performance.
  • Enhanced dependency caching to optimize build times.
  • Updated action versions and added workflow concurrency controls for better resource management.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

GitHub Actions workflows updated with concurrency control, action version bumps, and dependency caching. Dev workflow now includes npm cache configuration and test execution steps; release workflow adds release metadata flags.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflows Configuration ​.github/workflows/dev.yml, ​.github/workflows/release.yml	Dev workflow: Added concurrency control, bumped checkout (v6→v6.0.1) and setup-node (v6→v6.1.0), enabled npm caching, added npm install and test steps. Release workflow: Added concurrency block, bumped checkout (v6→v6.0.1) with fetch-depth, bumped release action (v2.5.0), added draft and prerelease flags.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify action version compatibility and changelog for each bump (checkout, setup-node, action-gh-release)
• Confirm npm cache configuration doesn't conflict with existing workflow state
• Validate concurrency group naming and cancel-in-progress behavior in both workflows

Possibly related PRs

• Release workflow #50: Directly modifies ​.github/workflows/release.yml with release workflow and action-gh-release updates.
• CI tests #40: Directly modifies ​.github/workflows/dev.yml with CI workflow configuration changes.

Poem

🐰 With workflows so crisp and actions so spry,
We cache our dependencies, watch builds fly high!
Concurrency reins in the chaos we knew,
Fresh action versions—the builds feel brand new! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update workflows' is vague and generic, lacking specificity about what changes were made to the workflows.	Consider a more specific title such as 'Update GitHub Actions workflows with concurrency control and dependency caching' or 'Improve workflow reliability with action version updates and npm caching'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/ds-update-workflows

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ea22fe1 and 3fc37ff.

📒 Files selected for processing (2)

• .github/workflows/dev.yml (2 hunks)
• .github/workflows/release.yml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Codacy Static Code Analysis

🔇 Additional comments (7)

.github/workflows/release.yml (3)

8-10: Concurrency configuration is appropriate for release workflow.

The cancel-in-progress: false setting ensures that ongoing releases are not cancelled when a new tag is pushed, which is the correct behavior for production releases.

---

22-24: fetch-depth: 0 correctly enables full git history for release notes generation.

The setting ensures that generate_release_notes: true (line 29) has complete git history to generate comprehensive release notes from all commits.

---

27-27: Release metadata flags are correctly configured.

The draft: false and prerelease: false flags explicitly ensure published releases are marked as final, aligning with production release best practices. The action version v2.5.0 (released Dec 1, 2025) is current and includes improvements for draft release handling.

.github/workflows/dev.yml (4)

10-12: Concurrency configuration is appropriate for dev workflow.

The cancel-in-progress: true setting correctly cancels older CI runs when new commits arrive, reducing redundant test execution and speeding up developer feedback loops.

---

40-44: npm ci and test steps follow CI/CD best practices.

Using npm ci over npm install is the correct choice for automated environments, ensuring deterministic and reproducible builds. The test step execution aligns with the dev workflow's purpose.

---

32-32: npm cache configuration optimizes workflow performance.

The cache: npm setting leverages GitHub Actions' dependency caching to speed up subsequent workflow runs by caching node_modules and package-lock.json. actions/setup-node@v6.1.0 includes built-in npm caching support and automatically enables it when package.json contains a packageManager field or devEngines.packageManager set to "npm". This works correctly across the Node version matrix [20, 22, 24].

---

29-29: Checkout action version update is correct and appropriate.

The actions/checkout@v6.0.1 version is stable with no breaking changes. The default shallow clone (fetch-depth: 1) is suitable for the dev workflow since full git history is unnecessary for test execution.

---

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 and usage tips.}