chore(deps): autoupdate 2026-06-21

[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 dependency in example application.

[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: dd36e876-43a6-45cc-8397-386bc6211de2

📥 Commits

Reviewing files that changed from the base of the PR and between cd9c4d9 and 3c9e5da.

⛔ 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 development dependency in examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json is bumped from ^22.2.6 to ^22.2.7.

Changes

Dependency Version Bump

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

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• forge-sql-orm/atlassian-runtime-bridge#33: Previous bump of the same npm-check-updates devDependency in the same package.json file.
• forge-sql-orm/atlassian-runtime-bridge#37: Another direct version bump of npm-check-updates in the same devDependencies field.
• forge-sql-orm/atlassian-runtime-bridge#46: Immediately preceding bump of npm-check-updates to a ^22.2.x version in the same file with no other changes.

Poem

🐇 A tiny hop, a patch goes by,
npm-check-updates climbs a notch high,
From .6 to .7 we bounce with glee,
A rabbit's garden, dependency-free!
Small steps forward, one line at a time~ 🌿

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is significantly incomplete compared to the template; it lacks Summary, Type of change, Modules touched, and Testing sections.	Fill out the PR template with required sections including what changed, type of change, modules affected, and testing confirmation.
Title check	❓ Inconclusive	The title is vague and generic, using 'autoupdate' and a date without specifying the actual dependency change (npm-check-updates bump).	Consider a more descriptive title like 'chore(deps): bump npm-check-updates to 22.2.7' to clarify the specific change.

✅ Passed checks (3 passed)

Check name	Status	Explanation
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-21

---

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.