deps: all non-major dependencies - #759
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThe pull request updates Node and pnpm tooling from 11.16.0 to 11.17.0 across workflows and package metadata, and bumps selected runtime and development dependencies. ChangesVersion refresh
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install timed out. The project may have too many dependencies for the sandbox. 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 81: Add a tracked Node runtime version file using Node 22.22.1 or newer
to satisfy lint-staged@17.2.0, unless the project must support an older runtime;
in that case, replace the lint-staged version in package.json with one
compatible with the supported Node version.
- Line 5: Update the `@aws-sdk/client-ses` dependency in package.json from
3.1094.0 to the latest stable 3.1095.0, then regenerate the pnpm lockfile so the
resolved package metadata matches.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 758a2795-e98e-4153-b860-fe00d951ff68
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (4)
.github/workflows/ci.yml.github/workflows/crawl.yml.github/workflows/deploy-sanity.ymlpackage.json
| "version": "1.0.0", | ||
| "private": true, | ||
| "packageManager": "pnpm@11.16.0", | ||
| "packageManager": "pnpm@11.17.0", |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
for spec in \
'pnpm@11.17.0' \
'`@aws-sdk/client-ses`@3.1094.0' \
'lucide-react@1.26.0' \
'next-sanity@13.2.1' \
'lint-staged@17.2.0'
do
package="${spec%@*}"
selected="${spec##*@}"
latest="$(npm view "$package" dist-tags.latest)"
npm view "$package@$selected" version >/dev/null
printf '%-28s selected=%-10s latest=%s\n' "$package" "$selected" "$latest"
doneRepository: dejanvasic85/williamstownsc
Length of output: 1973
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
printf 'package.json dependency lines:\n'
rg -n '"(pnpm|`@aws-sdk/client-ses`|lucide-react|next-sanity|lint-staged)"' package.json
printf '\nlockfile entries:\n'
rg -n '(`@aws-sdk/client-ses`|lucide-react|next-sanity|lint-staged|pnpm:)' pnpm-lock.yaml package.json 2>/dev/null || true
printf '\nnode/tooling versions:\n'
{ [ -f .nvmrc ] && cat .nvmrc; [ -f .node-version ] && cat .node-version; [ -f .mise.toml ] && cat .mise.toml; [ -f .tool-versions ] && cat .tool-versions; } 2>/dev/null || true
printf '\nregistry latest vs selected headroom:\n'
for pkg in '`@aws-sdk/client-ses`' 'next-sanity' 'lint-staged' 'lucide-react' 'pnpm'; do
npm view "$pkg" version name version
doneRepository: dejanvasic85/williamstownsc
Length of output: 2277
Update @aws-sdk/client-ses to the latest stable version.
pnpm, lucide-react, next-sanity, and lint-staged match npm’s latest dist-tag, but @aws-sdk/client-ses is selected at 3.1094.0 while latest is 3.1095.0. Update it in package.json and regenerate the lockfile.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 5, Update the `@aws-sdk/client-ses` dependency in
package.json from 3.1094.0 to the latest stable 3.1095.0, then regenerate the
pnpm lockfile so the resolved package metadata matches.
Sources: Coding guidelines, MCP tools
| "eslint-plugin-import": "2.32.0", | ||
| "husky": "9.1.7", | ||
| "lint-staged": "17.1.1", | ||
| "lint-staged": "17.2.0", |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
fd -HI -t f '^(mise\.toml|\.node-version|\.nvmrc|package\.json|.*\.yml)$' . \
-x rg -n -H 'node(js)?|mise|pnpm' {}Repository: dejanvasic85/williamstownsc
Length of output: 50384
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
echo "top-level tracked config files:"
git ls-files | rg '(^|/)(mise\.toml|\.node-version|\.nvmrc|\.tool-versions|package\.json|pnpm-lock\.yaml|package-lock\.json|yarn\.lock)$' || true
echo
echo "node-related top-level/config matches:"
git ls-files | rg '(^|/)(mise\.toml|\.node-version|\.nvmrc|\.tool-versions|package\.json|pnpm-lock\.yaml|package-lock\.json|yarn\.lock)$' | \
xargs -r -n1 sh -c 'echo "--- $1"; rg -n -H -m 10 "^(node|Node|NODE|nodejs|engines|volta|toolset|mise|pnpm@|lint-staged@|lint-staged:)" "$1" || true' sh {}
echo
echo "lint-staged and lock entries:"
rg -n -H '"lint-staged"|lint-staged@' package.json pnpm-lock.yaml 2>/dev/null || trueRepository: dejanvasic85/williamstownsc
Length of output: 606
🌐 Web query:
npm lint-staged 17.2.0 engines node
💡 Result:
As of version 17.2.0, lint-staged requires Node.js version 22.22.1 or higher [1][2][3]. This requirement was introduced in version 17.0.0, which dropped support for Node.js v20 [1][2][3]. You can use any active Long Term Support (LTS) version of Node.js from v22 onwards [1][2][3].
Citations:
- 1: https://github.com/lint-staged/lint-staged/blob/HEAD/CHANGELOG.md
- 2: https://github.com/okonet/lint-staged/blob/v17.0.7/MIGRATION.md
- 3: https://github.com/lint-staged/lint-staged/blob/main/MIGRATION.md
Add or update the project Node runtime to satisfy lint-staged@17.2.0.
lint-staged@17.2.0 requires Node >=22.22.1, and there is no tracked Node version file (mise.toml, .node-version, .nvmrc, or .tool-versions). Add one for CI/local dev with at least Node 22.22.1, or upgrade the dependency if an older Node runtime must be supported.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 81, Add a tracked Node runtime version file using Node
22.22.1 or newer to satisfy lint-staged@17.2.0, unless the project must support
an older runtime; in that case, replace the lint-staged version in package.json
with one compatible with the supported Node version.
1 participant
This PR contains the following updates:
3.1093.0→3.1094.03.1095.017.1.1→17.2.01.25.0→1.26.013.1.7→13.2.111.16.0→11.17.011.16.0→11.17.0Release Notes
aws/aws-sdk-js-v3 (@aws-sdk/client-ses)
v3.1094.0Compare Source
Note: Version bump only for package @aws-sdk/client-ses
lint-staged/lint-staged (lint-staged)
v17.2.0Compare Source
Minor Changes
#1823
ee156cc- The chunking of tasks based on maximum command line argument length has been re-implemented to be more precise. Now the chunking happens based on the final generated command string, instead of just the list of staged files like previously. This benefits mainly Windows platforms and function commands like:Where the spawned command is literally
"tsc"without any extra arguments. Previously, this was still chunked when a lot of files were staged. Now, it probably won't be chunked because the length of the command is just three letters.Also, native JavaScript/Node.js function tasks won't be chunked at all, when previously they were run multiple times when chunked:
lucide-icons/lucide (lucide-react)
v1.26.0: Version 1.26.0Compare Source
What's Changed
columns-3-cogicon by @kamilasw in #4578adicon by @karsa-mistmere in #4579book-openicons by @karsa-mistmere in #4565shield-keyholeicon by @karsa-mistmere in #4580New Contributors
Full Changelog: lucide-icons/lucide@1.25.0...1.26.0
sanity-io/next-sanity (next-sanity)
v13.2.1Compare Source
Patch Changes
e32d6c7Thanks @renovate! - fix(deps): update dependency @portabletext/react to v7v13.2.0Compare Source
Minor Changes
54fb137Thanks @pedrobonamin! - Add editing variant support: persist the variant selected in the Presentation tool in asanity-preview-variantcookie (viadefineEnableDraftModeand the newvariantChangeActionwired toonVariantChange), resolve it with the newresolveVariantFromCookieshelper, and pass the newvariantoption throughsanityFetchtoclient.fetchso previews refetch with the selected variant.Patch Changes
1926bf8Thanks @renovate! - fix(deps): update dependency @sanity/visual-editing to ^5.7.2pnpm/pnpm (pnpm)
v11.17.0: pnpm 11.17Compare Source
Minor Changes
Added a new setting,
update.githubActionsServer, for specifying the base URL of the GitHub server that hosts the repositories of the GitHub Actions referenced by the workflow files (for example, a GitHub Enterprise Server). When the setting is not defined, the URL is read from theGITHUB_SERVER_URLenvironment variable, falling back tohttps://github.com. The URL must use thehttps://orhttp://protocol #13220.pnpm outdatedandpnpm updateno longer fail when the refs of a GitHub Action's repository cannot be read (for example, when the action's repository is private or hosted on a different GitHub server). Such actions are now skipped with a warning.Setting
update.githubActionstofalsenow makespnpm outdatedand the interactivepnpm updateskip GitHub Actions dependencies.Patch Changes
The token poll for web-based authentication no longer reads the body of non-OK or still-pending (HTTP 202) responses, and caps the token response body it does read at 64 KiB, so a malicious or compromised registry cannot exhaust memory through the poll pnpm/pnpm#12721.
Fixed
catalog:references in dependencies and overrides failing to resolve when installing through a pnpr server, which errored with "No catalog entry '' was found for catalog 'default'." even though the catalog entry existed. Also fixed a crash on Windows when installing a nested workspace member (e.g.packages/foo) through a pnpr server #13232.Republished every package: the tarballs published by the v11.13.1 through v11.16.0 releases were missing most of their compiled files due to a packing bug #13164.
Revert script ordering change for
pnpm run --sequential /regex/Support the
from-gitargument in thepnpm versioncommand.When the authentication URL cannot be rendered as a QR code (for example when it exceeds the maximum QR data capacity), web-based login now displays the URL alone with a warning instead of aborting authentication pnpm/pnpm#12721.
Platinum Sponsors
Gold Sponsors
Configuration
📅 Schedule: (in timezone Australia/Melbourne)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate.
Summary by CodeRabbit