chore(deps): autoupdate 2026-09-28

[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
  • This release includes a small maintenance update to the embedded app’s platform integration. No changes to the user-facing experience are included.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 6c776281-8459-41c8-8b04-dbb1c949e717

📥 Commits

Reviewing files that changed from the base of the PR and between 0e875a9 and 3557418.

⛔ 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: This review used your included allowance. 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 range from ^7.0.0 to ^7.1.0.

Changes

Forge Bridge Dependency

Layer / File(s)	Summary
Update the Forge Bridge dependency range examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json	The package manifest changes the @forge/bridge dependency range from ^7.0.0 to ^7.1.0.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 35574

The sample allows @forge/bridge 7.1.0, and both transport integrations remain compatible. No actionable merge risk was identified.

Architecture Summary

Architecture risk: 🔵 Low · up to 35574

The change affects 1 system.

Changed systems: examples

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — examples (ui) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json: The @forge/bridge dependency range changed from ^7.0.0 to ^7.1.0.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains that the change is an automated dependency update, but it omits the required Summary, type, modules, breaking change, testing, and checklist sections.	Complete the repository description template. State the dependency change and reason, mark the change type and Example / frontend module, confirm whether it is breaking, record testing or explain why tests were not run, and complete the che…

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies an automated dependency update and includes the update date. It is concise and related to the change.
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

Resolution

Complete the repository description template. State the dependency change and reason, mark the change type and Example / frontend module, confirm whether it is breaking, record testing or explain why tests were not run, and complete the checklist.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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.