Skip to content

chore(deps): update backstage to v6.2.2 (development)#262

Open
renovate[bot] wants to merge 1 commit into
developmentfrom
renovate/development-helmv3
Open

chore(deps): update backstage to v6.2.2 (development)#262
renovate[bot] wants to merge 1 commit into
developmentfrom
renovate/development-helmv3

Conversation

@renovate

@renovate renovate Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
backstage (source) minor 6.1.16.2.2

Release Notes

redhat-developer/rhdh-chart (backstage)

v6.2.2

Compare Source

A Helm chart for deploying Red Hat Developer Hub, which is a Red Hat supported version of Backstage. The telemetry data collection feature is enabled by default. Red Hat Developer Hub sends telemetry data to Red Hat by using the backstage-plugin-analytics-provider-segment plugin. To disable this and to learn what data is being collected, see https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.6/html-single/telemetry_data_collection_and_analysis/index

What's Changed

  • fix(orchestrator): lowercase and truncate DB creation Job name for compliance [RHDHBUGS-3329] by @​rm3l in #​466

Full Changelog: redhat-developer/rhdh-chart@backstage-6.2.1...backstage-6.2.2

v6.2.1

Compare Source

A Helm chart for deploying Red Hat Developer Hub, which is a Red Hat supported version of Backstage. The telemetry data collection feature is enabled by default. Red Hat Developer Hub sends telemetry data to Red Hat by using the backstage-plugin-analytics-provider-segment plugin. To disable this and to learn what data is being collected, see https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.6/html-single/telemetry_data_collection_and_analysis/index

What's Changed

Full Changelog: redhat-developer/rhdh-chart@backstage-6.2.0...backstage-6.2.1

v6.2.0

Compare Source

A Helm chart for deploying Red Hat Developer Hub, which is a Red Hat supported version of Backstage. The telemetry data collection feature is enabled by default. Red Hat Developer Hub sends telemetry data to Red Hat by using the backstage-plugin-analytics-provider-segment plugin. To disable this and to learn what data is being collected, see https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.6/html-single/telemetry_data_collection_and_analysis/index

What's Changed

New Contributors

Full Changelog: redhat-developer/rhdh-chart@backstage-6.1.3...backstage-6.2.0

v6.1.3

Compare Source

A Helm chart for deploying Red Hat Developer Hub, which is a Red Hat supported version of Backstage. The telemetry data collection feature is enabled by default. Red Hat Developer Hub sends telemetry data to Red Hat by using the backstage-plugin-analytics-provider-segment plugin. To disable this and to learn what data is being collected, see https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.6/html-single/telemetry_data_collection_and_analysis/index

What's Changed

Full Changelog: redhat-developer/rhdh-chart@backstage-6.1.2...backstage-6.1.3

v6.1.2

Compare Source

A Helm chart for deploying Red Hat Developer Hub, which is a Red Hat supported version of Backstage. The telemetry data collection feature is enabled by default. Red Hat Developer Hub sends telemetry data to Red Hat by using the backstage-plugin-analytics-provider-segment plugin. To disable this and to learn what data is being collected, see https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.6/html-single/telemetry_data_collection_and_analysis/index

What's Changed

Full Changelog: redhat-developer/rhdh-chart@backstage-6.1.1...backstage-6.1.2


Configuration

📅 Schedule: (in timezone America/Toronto)

  • Branch creation
    • Between 07:00 PM and 11:59 PM, only on Sunday (* 19-23 * * 0)
    • Between 12:00 AM and 02:59 AM, only on Monday (* 0-2 * * 1)
  • 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.

@renovate renovate Bot added the renovatebot label Jul 13, 2026
@renovate renovate Bot changed the title chore(deps): update backstage to v6.2.0 (development) Update backstage to v6.2.0 (development) Jul 13, 2026
@renovate renovate Bot changed the title Update backstage to v6.2.0 (development) chore(deps): update backstage to v6.2.0 (development) Jul 13, 2026
@gabemontero

Copy link
Copy Markdown
Contributor

do we think the unit tests here are sufficient for bumping the helm chart ?

or should some sort of testing on a personal cluster occur?

@renovate renovate Bot changed the title chore(deps): update backstage to v6.2.0 (development) Update backstage to v6.2.0 (development) Jul 13, 2026
@renovate renovate Bot changed the title Update backstage to v6.2.0 (development) chore(deps): update backstage to v6.2.0 (development) Jul 14, 2026
@renovate
renovate Bot force-pushed the renovate/development-helmv3 branch from a51fc78 to 9b81439 Compare July 15, 2026 13:29
@renovate renovate Bot changed the title chore(deps): update backstage to v6.2.0 (development) chore(deps): update backstage to v6.2.1 (development) Jul 15, 2026
@renovate renovate Bot changed the title chore(deps): update backstage to v6.2.1 (development) Update backstage to v6.2.1 (development) Jul 15, 2026
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
renovate Bot force-pushed the renovate/development-helmv3 branch from 9b81439 to 2ca9077 Compare July 15, 2026 19:16
@renovate renovate Bot changed the title Update backstage to v6.2.1 (development) Update backstage to v6.2.2 (development) Jul 15, 2026
@michael-valdron

Copy link
Copy Markdown
Contributor

do we think the unit tests here are sufficient for bumping the helm chart ?

or should some sort of testing on a personal cluster occur?

@gabemontero 6.2.0 should be fine as its in the rolling demo already, unsure though about 6.2.2 fwiw its a patch from 6.2.0.

As for testing, I think this might of been brought up before (cc @HusneShabbir), I could picture doing this with prow for testing deploying the chart on OpenShift, but I think we'll still need to onboard to that first.

@renovate renovate Bot changed the title Update backstage to v6.2.2 (development) chore(deps): update backstage to v6.2.2 (development) Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants