chore(deps): autoupdate 2026-08-17

[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 Forge bridge integration to the latest compatible release, improving compatibility with supported platform capabilities.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4eaa4eeb-3bb0-412a-a2ec-e30d46e51e02

📥 Commits

Reviewing files that changed from the base of the PR and between 6aa7042 and be466e0.

⛔ 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 includes up to 1 review per rolling hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The sample frontend upgrades the @forge/bridge dependency from ^6.2.0 to ^6.3.0.

Changes

Forge bridge update

Layer / File(s)	Summary
Update Forge bridge dependency examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json	The frontend dependency declaration changes @forge/bridge from ^6.2.0 to ^6.3.0.

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

Merge Risk: ⚪ Minimal · up to be466

This PR updates frontend dependency manifests in the sample application, with no actionable merge-blocking risk identified; it is merge-ready after normal checks and review.

Possibly related PRs

• forge-sql-orm/atlassian-runtime-bridge#48: Updates @forge/bridge in the same frontend/package.json file.
• forge-sql-orm/atlassian-runtime-bridge#62: Updates @forge/bridge in the same frontend/package.json file.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description only explains the automation and auto-merge behavior; it omits the required summary, change type, modules, testing, and checklist sections.	Complete the repository template with the change summary, selected change type and module, breaking-change status, testing details, and checklist items.

✅ 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.
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-08-17

---

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.