Skip to content

Upgrade PostgreSQL 14 to 16 - #6035

Draft
hardillb wants to merge 7 commits into
mainfrom
postgresql-upgrade
Draft

hardillb wants to merge 7 commits into
mainfrom
postgresql-upgrade

Conversation

@hardillb

Copy link
Copy Markdown
Contributor

Description

Documentation for how to perform a PostgreSQL upgrade.

Still work in progress but raising for @sumitshinde-84 can assist with SEO headers

Related Issue(s)

Checklist

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • For blog PRs, an Art Request has been created (instructions)

@hardillb hardillb self-assigned this Nov 17, 2026
@netlify

netlify Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for flowfuse-website ready!

Name Link
🔨 Latest commit e2b6db3
🔍 Latest deploy log https://app.netlify.com/projects/flowfuse-website/deploys/6afc227d6f469b192496c761
😎 Deploy Preview https://deploy-preview-6035--flowfuse-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 61 (🟢 up 4 from production)
Accessibility: 98 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

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

@netlify

netlify Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for flowfuse-website ready!

Name Link
🔨 Latest commit ddf27f5
🔍 Latest deploy log https://app.netlify.com/projects/flowfuse-website/deploys/6afc228f6f469b192496c782
😎 Deploy Preview https://deploy-preview-6035--flowfuse-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 82 (🟢 up 25 from production)
Accessibility: 98 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

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

@netlify

netlify Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for flowfuse-website ready!

Name Link
🔨 Latest commit 5a9474d
🔍 Latest deploy log https://app.netlify.com/projects/flowfuse-website/deploys/6b002bd483608868ec98be5b
😎 Deploy Preview https://deploy-preview-6035--flowfuse-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 81 (🟢 up 17 from production)
Accessibility: 98 (no change from production)
Best Practices: 100 (no change from production)
SEO: 85 (no change from production)
PWA: -
View the detailed breakdown and full score reports

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

@hardillb hardillb changed the title Upgrade PostgreSQL 14 to 15 Upgrade PostgreSQL 14 to 16 Nov 17, 2026
@hardillb

Copy link
Copy Markdown
Contributor Author

@sumitshinde-84 this has all the required basic details in it now.

  • I can't work out why the tests are failing as I've not touched any of the failing files.
  • Need to work out what needs adding to the headers

This will be released Dec 18th, but we need to have it all ready to go early in case we need to pull it forward.

@sumitshinde-84

Copy link
Copy Markdown
Contributor

Hey Ben, found why the tests were failing on your PR. It wasn't your post. There's a bug in the site code that empties the blog listing whenever any post is scheduled for a future date. With the listing empty, the /blog/#sign-up anchor disappears and the link check fails on every page that links to it from the nav. main only passes because nothing else is scheduled right now.

I've opened a fix: #6041

@sumitshinde-84

Copy link
Copy Markdown
Contributor

I've opened a PR on top of your branch that adds the basic SEO elements and a short "action required" note near the top: #6042

On the new CTA: I don't think we need a new type. The CTA sits at the end of the post, so readers would only see it after they've done the upgrade. The "action required" note at the top covers that better, because they see the steps before they start. The end of the post keeps the Contact CTA, with wording about getting help with the upgrade.

Since this is an upgrade guide, it doesn't need heavy SEO, so I've kept it light. I'll add the blog hero image later.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants