chore(deps): autoupdate 2026-06-04

[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 Atlassian Connect dependency to the latest patch version.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7472624d-c73c-4743-b5ce-3f557e7254a5

📥 Commits

Reviewing files that changed from the base of the PR and between af54820 and 6d71497.

📒 Files selected for processing (1)

• pom.xml

---

📝 Walkthrough

Walkthrough

This PR updates the Atlassian Connect dependency version from 6.0.5 to 6.0.6 via a Maven property change in pom.xml. All managed dependencies referencing ${atlassian.connect.version} are affected by this single-line update.

Changes

Dependency Version Update

Layer / File(s)	Summary
Atlassian Connect version update pom.xml	Maven property atlassian.connect.version is bumped from 6.0.5 to 6.0.6, updating managed Atlassian Connect dependency versions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• forge-sql-orm/atlassian-runtime-bridge#34: Prior version bump of the same Maven property atlassian.connect.version from 6.0.4 to 6.0.5, following the same dependency update pattern.

Poem

🐰 A version bump hops into view,
From six-point-oh-five to six-point-oh-six, it's true!
Atlassian Connect now sings a newer tune,
Dependencies dance beneath the moon! 🌙

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description provided is minimal and does not follow the required template structure. Required sections like Summary, Type of change, Modules touched, How tested, and Checklist are all missing.	Complete the pull request description using the repository template. Include Summary, Type of change, Modules touched, How tested sections, and verify all checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore(deps): autoupdate 2026-06-04' accurately describes the changeset as an automated dependency update, though it is somewhat generic and doesn't specify which dependencies were updated.
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-04

---

_{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

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

This PR is an automated update that meets all quality standards. Codacy analysis confirms the changes are up to standards with no new issues or complexity increases. No major logic bugs or security risks were identified that would prevent merging.

Test suggestions

• Verify that the project compiles and passes existing integration tests with the new Atlassian Connect version

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that the project compiles and passes existing integration tests with the new Atlassian Connect version

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

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