chore(deps): autoupdate 2026-06-03

[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 dev dependency version for the sample application frontend.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 02663b3c-84e5-4ab6-8242-cc0a6c71524a

📥 Commits

Reviewing files that changed from the base of the PR and between 875b3e6 and 976fd7d.

⛔ 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

---

📝 Walkthrough

Walkthrough

The PR updates the npm-check-updates dev dependency from version ^22.2.1 to ^22.2.2 in the Forge Spring Boot example's frontend package configuration. This is a routine patch-level version bump with no changes to other dependencies, scripts, or configuration.

Changes

Dependency Version Update

Layer / File(s)	Summary
npm-check-updates patch bump examples/atlassian-connect-forge-spring-boot-sample/frontend/package.json	Dev dependency npm-check-updates is incremented from ^22.2.1 to ^22.2.2.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A carrot update hops through the file, 🥕
npm-check-updates marches on with a smile!
Twenty-two-two-two, a patch so minor,
The Spring Boot forge example shines ever finer. ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is largely incomplete compared to the template, missing Summary section details, Type of change selection, Modules touched, Testing information, and other required checklist items.	Complete the PR template by filling in the Summary section, selecting applicable change types and modules touched, documenting testing performed, and confirming all checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the automated dependency update action and includes the date, accurately summarizing the main change in this pull request.
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-03

---

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

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 performs an automated update of the npm-check-updates development dependency from version ^22.2.1 to ^22.2.2 in the frontend package.json file.

Codacy analysis indicates that the code remains up to standards, with no new issues or increases in complexity. No critical logic bugs or security risks were identified, and the implementation aligns with the intended automated chore.

Test suggestions

• Verify that npm-check-updates version is updated to ^22.2.2 in the frontend package.json

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