Conversation
chore(deps): update pnpm/action-setup action to v5
Bumps [eslint](https://github.com/eslint/eslint) from 10.0.3 to 10.1.0. - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](eslint/eslint@v10.0.3...v10.1.0) --- updated-dependencies: - dependency-name: eslint dependency-version: 10.1.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.0 to 4.1.1. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.1/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.1 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (2)
📝 WalkthroughWalkthroughUpdates CI workflows to use Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Pull request overview
Updates the repo’s development tooling and CI configuration, primarily by bumping lint/format/tooling dependencies and modernizing pnpm GitHub Action usage while extending CI to run on the dev branch.
Changes:
- Bump
@tsparticles/*configs,typescript-eslint,prettier-plugin-multiline-arrays, andwebpack-cli(major) along with lockfile refresh. - Update GitHub Actions workflows to use
pnpm/action-setup@v5and run CI ondevas well asmain. - Update the empty-project template’s devDependency versions to match the new tooling stack.
Reviewed changes
Copilot reviewed 4 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| pnpm-lock.yaml | Lockfile refresh to reflect updated tooling versions (incl. webpack-cli@7). |
| package.json | Package version bump to 3.3.8 and dependency/devDependency upgrades. |
| files/empty-project/package.json | Template devDependency upgrades (incl. webpack-cli@7). |
| .github/workflows/npm-publish.yml | Update pnpm action to pnpm/action-setup@v5.0.0. |
| .github/workflows/node.js-ci.yml | Run CI on dev branch and update pnpm action to pnpm/action-setup@v5. |
Files not reviewed (1)
- pnpm-lock.yaml: Language not supported
Comments suppressed due to low confidence (1)
.github/workflows/node.js-ci.yml:28
- Since this workflow is being updated to
pnpm/action-setup@v5, consider also updating theGet pnpm store directorystep to use$GITHUB_OUTPUTinstead of the deprecated::set-outputcommand; GitHub can disable::set-outputand it will break the cache path wiring.
- uses: pnpm/action-setup@v5
name: Install pnpm
id: pnpm-install
with:
run_install: false
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| with: | ||
| node-version: "24" | ||
| - uses: pnpm/action-setup@v4 | ||
| - uses: pnpm/action-setup@v5 |
There was a problem hiding this comment.
npm-publish.yml pins pnpm/action-setup to v5.0.0 but this workflow uses the floating @v5. For reproducible CI behavior, use the same pinned version (or a commit SHA) here too.
files/empty-project/package.json
Outdated
| "typescript-eslint": "^8.57.1", | ||
| "webpack": "^5.105.4", | ||
| "webpack-bundle-analyzer": "^5.2.0", | ||
| "webpack-cli": "^6.0.1" | ||
| "webpack-cli": "^7.0.2" |
There was a problem hiding this comment.
Bumping webpack-cli to ^7.0.2 raises the minimum Node requirement (lockfile shows webpack-cli@7.0.2 requires Node >=20.9.0). Since this template package.json doesn’t declare engines.node, users on older Node versions will hit install failures without a clear explanation—either add an engines field reflecting the new minimum or keep webpack-cli on v6 for broader compatibility.
…eslint-10.1.0 build(deps): bump eslint from 10.0.3 to 10.1.0
…vitest-4.1.1 build(deps-dev): bump vitest from 4.1.0 to 4.1.1
chore(deps): update dependency @swc/core to v1.15.21
Summary by CodeRabbit
Release Notes