Chart: use same bitnami postgres image as 1.18.0#61156
Merged
potiuk merged 1 commit intoapache:mainfrom Jan 28, 2026
Merged
Conversation
Instead of downgrading from 16 -> 13, lets just keep using the same exact bitnami image we had been previously. It's likely users of the provided postgres moved to this image anyways.
jedcunningham
requested review from
hussein-awala and
jscheffl
as code owners
potiuk
approved these changes
Jan 28, 2026
shreyas-dev
pushed a commit
to shreyas-dev/airflow
that referenced
this pull request
Jan 29, 2026
Instead of downgrading from 16 -> 13, lets just keep using the same exact bitnami image we had been previously. It's likely users of the provided postgres moved to this image anyways.
98 tasks
2 tasks
shashbha14
pushed a commit
to shashbha14/airflow
that referenced
this pull request
Feb 2, 2026
Instead of downgrading from 16 -> 13, lets just keep using the same exact bitnami image we had been previously. It's likely users of the provided postgres moved to this image anyways.
jason810496
pushed a commit
to abhijeets25012-tech/airflow
that referenced
this pull request
Feb 3, 2026
Instead of downgrading from 16 -> 13, lets just keep using the same exact bitnami image we had been previously. It's likely users of the provided postgres moved to this image anyways.
jhgoebbert
pushed a commit
to jhgoebbert/airflow_Owen-CH-Leung
that referenced
this pull request
Feb 8, 2026
Instead of downgrading from 16 -> 13, lets just keep using the same exact bitnami image we had been previously. It's likely users of the provided postgres moved to this image anyways.
choo121600
pushed a commit
to choo121600/airflow
that referenced
this pull request
Feb 22, 2026
Instead of downgrading from 16 -> 13, lets just keep using the same exact bitnami image we had been previously. It's likely users of the provided postgres moved to this image anyways.
Subham-KRLX
pushed a commit
to Subham-KRLX/airflow
that referenced
this pull request
Mar 4, 2026
Instead of downgrading from 16 -> 13, lets just keep using the same exact bitnami image we had been previously. It's likely users of the provided postgres moved to this image anyways.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Instead of downgrading from 16 -> 13, lets just keep using the same exact bitnami image we had been previously. It's likely users of the provided postgres moved to this image anyways.
Related: #55820
Was generative AI tooling used to co-author this PR?
Generated-by: Cursor (Claude Opus 4.5)