chore(deps): update helm release backstage to v2.6.0

[renovate]

This PR contains the following updates:

Package	Update	Change
backstage (source)	minor	2.5.3 -> 2.6.0

---

Release Notes

backstage/charts (backstage)

v2.6.0

Compare Source

A Helm chart for deploying a Backstage application

What's Changed

• feat: Support autoscaling via HPA by @​rm3l in https://github.com/backstage/charts/pull/268

Full Changelog: backstage/charts@backstage-2.5.3...backstage-2.6.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

Summary by Sourcery

Upgrade the Backstage Helm chart dependency to v2.6.0 to include new autoscaling support via HPA.

New Features:

• Support autoscaling via HPA in the Backstage Helm chart

Chores:

• Bump Backstage Helm chart dependency from v2.5.3 to v2.6.0

[sourcery-ai]

Reviewer's Guide

This PR upgrades the Backstage Helm chart dependency from v2.5.3 to v2.6.0 and updates the corresponding lock file to pull in the new release, which adds HPA-based autoscaling support.

Class diagram for Backstage Helm chart values with HPA support

classDiagram
  class BackstageValues {
    +string image
    +int replicaCount
    +HPAConfig hpa
    ...
  }
  class HPAConfig {
    +bool enabled
    +int minReplicas
    +int maxReplicas
    +object metrics
    ...
  }
  BackstageValues --> HPAConfig : hpa

Loading

File-Level Changes

Change	Details	Files
Bumped Backstage Helm chart dependency to v2.6.0	Update the upstream dependency version from 2.5.3 to 2.6.0 in Chart.yaml Regenerate Chart.lock to lock in the updated chart version	charts/backstage/Chart.yaml charts/backstage/Chart.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

⚠️ Files changed after running the pre-commit hooks

Those changes should have been pushed automatically to your PR branch.

NOTE: If the PR checks are stuck after this additional commit, manually close the PR and immediately reopen it to trigger the checks again.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[rm3l]

/bump minor

[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

[rm3l]

/lgtm