Skip to content

feat: update internal PostgreSQL to v16 #299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
zdrapela wants to merge 1 commit into from
Closed

feat: update internal PostgreSQL to v16 #299

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion charts/backstage/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,4 +47,4 @@ sources: []
# Versions are expected to follow Semantic Versioning (https://semver.org/)
# Note that when this chart is published to https://github.com/openshift-helm-charts/charts
# it will follow the RHDH versioning 1.y.z
version: 5.0.0
Copy link
Member Author

@zdrapela zdrapela Jan 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or should it be bumped rather to 6.0.0?

Copy link
Member

@subhashkhileri subhashkhileri Jan 19, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 i guess 5.1.0 is fine. since external DBs are unaffected.

Copy link
Member

@rm3l rm3l Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, to fix the CI failures (upgrade checks by default), I think we would need to bump it to 6.0.0: #299 (comment)
Which kinda makes sense from a user's perspective as this seems like a breaking change requiring manual intervention.

version: 5.1.0
4 changes: 2 additions & 2 deletions charts/backstage/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

# RHDH Backstage Helm Chart for OpenShift

![Version: 5.0.0](https://img.shields.io/badge/Version-5.0.0-informational?style=flat-square)
![Version: 5.1.0](https://img.shields.io/badge/Version-5.1.0-informational?style=flat-square)
![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)

A Helm chart for deploying Red Hat Developer Hub, which is a Red Hat supported version of Backstage.
Expand Down Expand Up @@ -30,7 +30,7 @@ helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo add backstage https://backstage.github.io/charts
helm repo add redhat-developer https://redhat-developer.github.io/rhdh-chart

helm install my-backstage redhat-developer/backstage --version 5.0.0
helm install my-backstage redhat-developer/backstage --version 5.1.0
```

## Introduction
Expand Down
2 changes: 1 addition & 1 deletion charts/backstage/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -274,7 +274,7 @@ upstream:
enabled: true
image:
registry: quay.io
repository: fedora/postgresql-15
repository: fedora/postgresql-16
Copy link
Member

@rm3l rm3l Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With hindsight, I'm wondering if we should actually proceed with this.. I've added this to the Cabal agenda for discussion.

tag: latest
auth:
secretKeys:
Expand Down
Loading