Upgrade to Ubuntu 26.04 LTS from 22.04

[jpmckinney]

22.04 is EOL Jun 2027. https://ubuntu.com/about/release-cycle

Upgrade servers: ./run.py '*' cmd.run 'lsb_release -a'

• kingfisher-main (Hetzner Dedicated): https://ocdsdeploy.readthedocs.io/en/latest/deploy/servers/data-support.html#create-a-data-support-main-server
• dream-bi (Hetzner Cloud): First time migrating. Double-check files to copy with @ndrhzn, and korsikov on Slack, and then document these on a new docs page.
• prometheus (Linode): https://ocdsdeploy.readthedocs.io/en/latest/deploy/servers/prometheus.html#migrate-from-an-old-server
• docs (Linode): https://ocdsdeploy.readthedocs.io/en/latest/deploy/servers/docs.html#migrate-from-an-old-server
• cms (Linode): First time migrating entire server, though we recently migrated the corporate site. We should create a page like those above, building off the steps in https://docs.google.com/document/d/1HyNXRgzLu-x6pHDQ4hkp5vEbvUm6S29lyNbMTXeO4yY/edit?tab=t.0#heading=h.hv00oifa1gte

@jpmckinney: Change the Python versions in relevant GitHub Actions workflows and other files. 26.04 ships with 3.13. Some apps create a venv using the default Python version:

• collect-generic
• kingfisher-collect and bi.open-contracting.org/powerbi/Dockerfile_python
• kingfisher-summarize

@yolile Last time we migrated kingfisher-main, we didn't keep any of the Process, Summarize or Pelican data, or any files in local-load directories. We only kept the incremental crawl data. Do we want to do anything differently this time? (Slack)

[RobHooper]

The current estimated release of 26.04 is 23 Apr 2026.
We should wait for the production ready release (".1") before migrating server. This is usually released in August / summer time.
We can start updating and reviewing the core SaltStack for any feature changes on the new release.

[yolile]

@yolile Last time we migrated kingfisher-main, we didn't keep any of the Process, Summarize or Pelican data, or any files in local-load directories. We only kept the incremental crawl data. Do we want to do anything differently this time?

Yes, I think we should preserve Kingfisher Process data. We often need that one to compare if previous publications have improved (we are at the beginning of the year, so this is very relevant). We can re-run the others (Summarize, Pelican) as needed

[jpmckinney]

Sounds good, @yolile. We can check with the rest of the data team on Slack when we're closer to the migration date.

[jpmckinney]

For cms, www.open-spending.eu uses the Modern Image Formats plugin, which currently can't enable AVIF support due to old imagemagick and libheif.

• Change Image output format to AVIF at https://www.open-spending.eu/wp-admin/options-media.php#modern-image-formats
• Check "Use <picture> element"
• wp media regenerate --yes
• wp cache flush
• "Purge Cache" at https://www.open-spending.eu/wp-admin/admin.php?page=super-page-cache
• Verify it's working
  • wp post meta get <id> _wp_attachment_metadata | grep -i avif shows image/avif
  • DevTools > Network shows .avif files
• Verify these render the same:
  • homepage: images in campaign cards, news cards, who-we-are members, org slider
  • campaign or news post: hero image and in-content block images
  • members page: org logos on organizations tab
  • about us page: in-content image

Edit: Wordpress 7.1 now has some built in webp and avif support: https://make.wordpress.org/core/2026/07/22/client-side-media-processing-in-wordpress-7-1/

[jpmckinney]

When we upgrade PHP, update the one version mentioned in .phpcs.xml.dist