Skip to content

feat!(deps): bump postgresql from 16 to 17#37782

Open
RealGreenDragon wants to merge 1 commit intoapache:masterfrom
RealGreenDragon:pg17
Open

feat!(deps): bump postgresql from 16 to 17#37782
RealGreenDragon wants to merge 1 commit intoapache:masterfrom
RealGreenDragon:pg17

Conversation

@RealGreenDragon
Copy link
Contributor

SUMMARY

This PR bumps PostgreSQL image version in Dockerfile and GH workflows from postgresql:16 to postgresql:17.

Also this PR bumps Helm Chart postgresql to v16.7.27 (latest v16 release) as it uses PostgreSQL 17 (declared here).

PostgreSQL 17.0 change log: https://www.postgresql.org/docs/release/17.0/

Documentation has been updated accordingly as done in #32597 .

Inspired by discussion #33943 .

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A

TESTING INSTRUCTIONS

N/A

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@github-actions github-actions bot added doc Namespace | Anything related to documentation github_actions Pull requests that update GitHub Actions code labels Feb 7, 2026
@dosubot dosubot bot added the install:config Installation - Configuration settings label Feb 7, 2026
@netlify
Copy link

netlify bot commented Feb 7, 2026

Deploy Preview for superset-docs-preview ready!

Name Link
🔨 Latest commit 136ef0d
🔍 Latest deploy log https://app.netlify.com/projects/superset-docs-preview/deploys/6987639a3b915500085ac3df
😎 Deploy Preview https://deploy-preview-37782--superset-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@codecov
Copy link

codecov bot commented Feb 7, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 66.21%. Comparing base (f4708a5) to head (d213872).
⚠️ Report is 6 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #37782       +/-   ##
===========================================
+ Coverage        0   66.21%   +66.21%     
===========================================
  Files           0      647      +647     
  Lines           0    49542    +49542     
  Branches        0     5568     +5568     
===========================================
+ Hits            0    32805    +32805     
- Misses          0    15435    +15435     
- Partials        0     1302     +1302     
Flag Coverage Δ
hive 41.73% <ø> (?)
mysql 64.28% <ø> (?)
postgres 64.36% <ø> (?)
presto 41.75% <ø> (?)
python 66.18% <ø> (?)
sqlite 64.05% <ø> (?)
unit 100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@bito-code-review bito-code-review bot left a comment

Choose a reason for hiding this comment

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

Code Review Agent Run #bec56c

Actionable Suggestions - 1
  • docs/docs/configuration/configuring-superset.mdx - 1
Review Details
  • Files reviewed - 3 · Commit Range: 136ef0d..136ef0d
    • docs/docs/configuration/configuring-superset.mdx
    • helm/superset/Chart.lock
    • helm/superset/Chart.yaml
  • Files skipped - 11
    • .github/workflows/superset-app-cli.yml - Reason: Filter setting
    • .github/workflows/superset-applitool-cypress.yml - Reason: Filter setting
    • .github/workflows/superset-e2e.yml - Reason: Filter setting
    • .github/workflows/superset-playwright.yml - Reason: Filter setting
    • .github/workflows/superset-python-integrationtest.yml - Reason: Filter setting
    • .github/workflows/superset-python-presto-hive.yml - Reason: Filter setting
    • docker-compose-image-tag.yml - Reason: Filter setting
    • docker-compose-light.yml - Reason: Filter setting
    • docker-compose-non-dev.yml - Reason: Filter setting
    • docker-compose.yml - Reason: Filter setting
    • helm/superset/README.md - Reason: Filter setting
  • Tools
    • Whispers (Secret Scanner) - ✔︎ Successful
    • Detect-secrets (Secret Scanner) - ✔︎ Successful

Bito Usage Guide

Commands

Type the following command in the pull request comment and save the comment.

  • /review - Manually triggers a full AI review.

  • /pause - Pauses automatic reviews on this pull request.

  • /resume - Resumes automatic reviews.

  • /resolve - Marks all Bito-posted review comments as resolved.

  • /abort - Cancels all in-progress reviews.

Refer to the documentation for additional commands.

Configuration

This repository uses Superset You can customize the agent settings here or contact your Bito workspace admin at evan@preset.io.

Documentation & Help

AI Code Review powered by Bito Logo

| [MySQL](https://www.mysql.com/) | 5.7, 8.X |
| Database Engine | Supported Versions |
| ----------------------------------------- | ---------------------------------------------- |
| [PostgreSQL](https://www.postgresql.org/) | 10.X, 11.X, 12.X, 13.X, 14.X, 15.X, 16.X, 17.X |
Copy link
Contributor

Choose a reason for hiding this comment

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

Inaccurate Version Listing

The documentation lists PostgreSQL 17.X as supported, but official Superset docs only list versions up to 16.X. While psycopg2 2.9.9 supports PostgreSQL 17, Superset's official documentation does not include it, so this addition may mislead users.

Code suggestion
Check the AI-generated fix before applying
Suggested change
| [PostgreSQL](https://www.postgresql.org/) | 10.X, 11.X, 12.X, 13.X, 14.X, 15.X, 16.X, 17.X |
| [PostgreSQL](https://www.postgresql.org/) | 10.X, 11.X, 12.X, 13.X, 14.X, 15.X, 16.X |

Code Review Run #bec56c


Should Bito avoid suggestions like this for future reviews? (Manage Rules)

  • Yes, avoid them

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This PR is to add PostgreSQL 17.X support.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, this PR adds PostgreSQL 17.X support by updating CI/CD workflows, Docker Compose files, documentation, and Helm charts to use PostgreSQL 17. A review comment suggests removing 17.X from the docs since official Superset documentation only lists up to 16.X.

@hainenber
Copy link
Contributor

Thanks for opening the PR @RealGreenDragon. There's a failed CI check with out-of-sync Chart lockfile. Can you run helm dependency update in the Charts folder to fix said issue?

@hainenber hainenber changed the title chore(deps): bump postgresql from 16 to 17 feat!(deps): bump postgresql from 16 to 17 Feb 8, 2026
@hainenber hainenber added risk:db-migration PRs that require a DB migration risk:breaking-change Issues or PRs that will introduce breaking changes labels Feb 8, 2026
@github-actions github-actions bot removed the risk:db-migration PRs that require a DB migration label Feb 8, 2026
@RealGreenDragon
Copy link
Contributor Author

Thanks for opening the PR @RealGreenDragon. There's a failed CI check with out-of-sync Chart lockfile. Can you run helm dependency update in the Charts folder to fix said issue?

Sorry, I missed that, Charts.lock is now updated.

@bito-code-review
Copy link
Contributor

bito-code-review bot commented Feb 8, 2026

Code Review Agent Run #1c7777

Actionable Suggestions - 0
Review Details
  • Files reviewed - 3 · Commit Range: d213872..d213872
    • docs/docs/configuration/configuring-superset.mdx
    • helm/superset/Chart.lock
    • helm/superset/Chart.yaml
  • Files skipped - 11
    • .github/workflows/superset-app-cli.yml - Reason: Filter setting
    • .github/workflows/superset-applitool-cypress.yml - Reason: Filter setting
    • .github/workflows/superset-e2e.yml - Reason: Filter setting
    • .github/workflows/superset-playwright.yml - Reason: Filter setting
    • .github/workflows/superset-python-integrationtest.yml - Reason: Filter setting
    • .github/workflows/superset-python-presto-hive.yml - Reason: Filter setting
    • docker-compose-image-tag.yml - Reason: Filter setting
    • docker-compose-light.yml - Reason: Filter setting
    • docker-compose-non-dev.yml - Reason: Filter setting
    • docker-compose.yml - Reason: Filter setting
    • helm/superset/README.md - Reason: Filter setting
  • Tools
    • Whispers (Secret Scanner) - ✔︎ Successful
    • Detect-secrets (Secret Scanner) - ✔︎ Successful

Bito Usage Guide

Commands

Type the following command in the pull request comment and save the comment.

  • /review - Manually triggers a full AI review.

  • /pause - Pauses automatic reviews on this pull request.

  • /resume - Resumes automatic reviews.

  • /resolve - Marks all Bito-posted review comments as resolved.

  • /abort - Cancels all in-progress reviews.

Refer to the documentation for additional commands.

Configuration

This repository uses Superset You can customize the agent settings here or contact your Bito workspace admin at evan@preset.io.

Documentation & Help

AI Code Review powered by Bito Logo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Namespace | Anything related to documentation github_actions Pull requests that update GitHub Actions code install:config Installation - Configuration settings risk:breaking-change Issues or PRs that will introduce breaking changes size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants