chore(deps): autoupdate 2026-06-06

[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 npm-check-updates development dependency to the latest patch version
  • Updated JaCoCo build tooling to the latest patch version

[coderabbitai]

Need the big picture first? Review this PR in Change Stack to see what changed before going file by file.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: eb2e03e4-1227-4237-80a3-d74d8e054e33

📥 Commits

Reviewing files that changed from the base of the PR and between 255c11c and 1f799cb.

⛔ 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 (2)

• examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json
• pom.xml

---

📝 Walkthrough

Walkthrough

The pull request updates two minor dependency versions: npm-check-updates in the frontend sample from 22.2.2 to 22.2.3, and the JaCoCo Maven plugin from 0.8.14 to 0.8.15. No functional changes are introduced.

Changes

Dependency Version Updates

Layer / File(s)	Summary
Frontend npm-check-updates version bump examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json	devDependencies.npm-check-updates is updated from ^22.2.2 to ^22.2.3.
Maven JaCoCo plugin version update pom.xml	jacoco.version property is updated from 0.8.14 to 0.8.15.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• forge-sql-orm/atlassian-runtime-bridge#33: Updates npm-check-updates in the same frontend package.json file from ^22.2.1 to ^22.2.2, continuing the version increment chain.

Poem

🐰 A rabbit hops through dependencies so small,
Two version bumps: npm and JaCoCo's call,
From 22.2.2 up to .3 we go,
And coverage tools get a gentle flow,
Minor but mighty, like carrots in spring! 🥕

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description lacks required sections from the template (Summary, Type of change, Modules touched, Testing, Checklist) and provides minimal context about the specific changes.	Complete the PR template with sections for Summary, Type of change, Modules touched, How tested, and Checklist to meet repository requirements.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly indicates this is an automated dependency update with the date stamp, which directly matches the changeset content.
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-06

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

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

[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

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