chore(deps): autoupdate 2026-06-29

[vzakharchenko]

Automated dependency update produced by .github/workflows/autoupdate.yml via scripts/update-dependencies.sh. Will auto-merge once required checks pass (see .github/workflows/automerge.yml).

Summary by CodeRabbit

• Chores
  • Updated a development dependency to the latest patch version.
  • No user-facing behavior, features, or scripts were changed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7ab13fa6-c395-4ebb-95b8-9079f2a218a3

📥 Commits

Reviewing files that changed from the base of the PR and between c724700 and a1eb13a.

⛔ Files ignored due to path filters (1)

• examples/atlassian-connect-forge-spring-boot-sample/frontend/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json

---

📝 Walkthrough

Walkthrough

The npm-check-updates dev dependency in the frontend package.json is bumped from ^22.2.8 to ^22.2.9. No other changes.

Changes

Dependency bump

Layer / File(s)	Summary
npm-check-updates patch bump examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json	npm-check-updates in devDependencies updated from ^22.2.8 to ^22.2.9.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

Possibly related PRs

• forge-sql-orm/atlassian-runtime-bridge#33: Same file, same dependency bumped by one patch version.
• forge-sql-orm/atlassian-runtime-bridge#47: Same file, same dependency bumped by one patch version.
• forge-sql-orm/atlassian-runtime-bridge#46: Same file, same dependency bumped by one patch version.

Poem

🐇 A tiny hop, a patch so small,
npm-check-updates gets a new call,
From .8 to .9 we leap with glee,
The freshest deps are plain to see!
thump thump — done! 🥕

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is too brief and misses nearly all required template sections, including summary, type, modules, testing, and checklist.	Fill in the template sections with a summary, issue link, change type, touched modules, breaking-change status, test steps, and checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the main change: an automated dependency update on 2026-06-29.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependencies/auto-2026-06-29

---

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.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[qltysh]

Coverage Impact

This PR will not change total coverage.

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.