chore(deps): autoupdate 2026-08-03 - #62
Conversation
📝 WalkthroughWalkthroughThe frontend dependency manifest updates ChangesFrontend dependencies
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
Up to standards ✅🟢 Issues
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json`:
- Line 26: Update the frontend package metadata to declare a Node.js baseline
compatible with npm-check-updates@23.0.1, using the engines.node field in
package.json or an equivalent tracked version file. If the project must support
older Node versions, instead pin npm-check-updates to a compatible release and
keep package.json and package-lock.json consistent.
🪄 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: b6c97f9f-85db-4a6c-bd1e-8986a4c96a20
⛔ Files ignored due to path filters (1)
examples/atlassian-connect-forge-spring-boot-sample/frontend/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json
| "@types/react-dom": "19.2.3", | ||
| "esbuild": "^0.28.1", | ||
| "npm-check-updates": "^23.0.0", | ||
| "npm-check-updates": "^23.0.1", |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
fd -H -t f . | rg '(^|/)(package\.json|package-lock\.json|\.nvmrc|\.node-version|\.tool-versions|Dockerfile.*|.*\.(yml|yaml))$' |
while IFS= read -r file; do
rg -n -C2 'engines|node-version|setup-node|NODE_VERSION|22\.22\.2|24\.15\.0|>=26' "$file" || true
doneRepository: forge-sql-orm/atlassian-runtime-bridge
Length of output: 18077
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Tracked Node version files and frontend package.json engines/scripts:"
for f in .nvmrc .node-version .tool-versions; do
if [ -f "$f" ]; then
echo "--- $f"
cat -n "$f"
fi
done
echo "--- examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json"
sed -n '1,80p' examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json | cat -n
echo "--- Workflow YAML Node actions/Node versions"
fd -H -t f . | rg '(^|/)\.github/workflows/.*\.(yml|yaml)$' | while IFS= read -r file; do
echo "--- $file"
rg -n -C3 'setup-node|node-version|node-version-file|npm-check-updates|npm|node|20|22|24|26' "$file" || true
done
echo "--- Any npm-check-updates commands in workflows/package scripts"
rg -n 'npm-check-updates|ncu' Examples examples .github package.json examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json || true
echo "--- git diff stat/name (if available)"
git diff --stat -- examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json examples/atlassian-connect-forge-spring-boot-sample/frontend/package-lock.json 2>/dev/null || true
git diff -- examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json 2>/dev/null | sed -n '1,120p' || trueRepository: forge-sql-orm/atlassian-runtime-bridge
Length of output: 6266
Raise the frontend Node baseline to match npm-check-updates@23.
examples/atlassian-connect-forge-spring-boot-sample/frontend/package-lock.json requires node: "^22.22.2 || ^24.15.0 || >=26.0.0" for npm-check-updates@23.0.1, but examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json has no engines.node field and no tracked .nvmrc/.node-version. If older Node versions are supported, set the frontend Node baseline accordingly or keep a compatible NCU version.
🤖 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 `@examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json` at
line 26, Update the frontend package metadata to declare a Node.js baseline
compatible with npm-check-updates@23.0.1, using the engines.node field in
package.json or an equivalent tracked version file. If the project must support
older Node versions, instead pin npm-check-updates to a compatible release and
keep package.json and package-lock.json consistent.
|
|
Coverage Impact This PR will not change total coverage. 🚦 See full report on Qlty Cloud »🛟 Help
|
1 participant
Automated dependency update produced by
.github/workflows/autoupdate.ymlviascripts/update-dependencies.sh. Will auto-merge once required checks pass (see.github/workflows/automerge.yml).Summary by CodeRabbit