chore(deps): autoupdate 2026-09-14

[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 the frontend integration library to a newer major version.
  • No direct user-facing feature or behavior changes are included in this update.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 1703ac8e-6139-4428-8ca1-483887fa6823

📥 Commits

Reviewing files that changed from the base of the PR and between 584015f and 9f8e6f9.

⛔ 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

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The sample frontend updates its @forge/bridge dependency from ^6.3.1 to ^7.0.0.

Changes

Forge bridge dependency update

Layer / File(s)	Summary
Update Forge bridge dependency examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json	The frontend now requires @forge/bridge version ^7.0.0 instead of ^6.3.1.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 9f8e6

The dependency update has no supported unresolved issue and is ready to merge after normal checks pass.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains that automation created the dependency update and that auto-merge is configured, but it omits the required Summary, issue reference, change type, modules touched, breaking cha…	Complete the repository template. State the @forge/bridge update from ^6.3.1 to ^7.0.0, mark the sample app and frontend module, identify whether the change is breaking, record the tests that ran, and complete the checklist.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies an automated dependency update and includes the update date.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

Full details: Description check

Explanation

The description explains that automation created the dependency update and that auto-merge is configured, but it omits the required Summary, issue reference, change type, modules touched, breaking change, testing, and checklist sections.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependencies/auto-2026-09-14

---

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.