chore(deps): autoupdate 2026-06-20

[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 development dependencies to the latest patch version.

[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: c12e3e4d-c47d-47c0-9131-3068e90c239e

📥 Commits

Reviewing files that changed from the base of the PR and between ee35a58 and c148e3b.

⛔ 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 devDependency in examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json is bumped from ^22.2.3 to ^22.2.6. No other files or dependencies are modified.

Changes

Frontend devDependency Bump

Layer / File(s)	Summary
npm-check-updates version update examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json	npm-check-updates devDependency version bumped from ^22.2.3 to ^22.2.6.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• forge-sql-orm/atlassian-runtime-bridge#33: Updates the same npm-check-updates devDependency in the same frontend/package.json file (previous bump: ^22.2.1 → ^22.2.2).
• forge-sql-orm/atlassian-runtime-bridge#37: Updates the same npm-check-updates devDependency in the same frontend/package.json file (previous bump: ^22.2.2 → ^22.2.3).

Poem

🐇 A tiny hop, a patch or three,
ncu bumps along merrily,
From .3 to .6 we go,
Keeping dependencies in the flow,
Small steps forward, says this bunny! 🌿

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is minimal but addresses automated dependency updates. It lacks required template sections (Summary details, Type of change, Modules touched, Testing steps, Checklist).	Complete the PR description template by adding Summary context, selecting Type of change checkboxes, specifying Modules touched, confirming testing performed, and completing the Checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore(deps): autoupdate 2026-06-20' accurately describes the main change: an automated dependency update with a timestamp.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

---

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

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