26.10.0

What's new since 26.8.1

Highlights

• [#215] Fixed 'seed.sh' printing a broken Docker Hub link and skipping ':latest' for destination images on other registries. @AlexSkrypnyk (#216)
  seed.sh now reports destinations on other registries correctly: a run that pushes to GHCR, a self-hosted registry or localhost:5055 ends on the pushed image reference instead of a Docker Hub link that 404s, and a docker.io/ prefix no longer ends up inside the Docker Hub link. An untagged destination on a registry with a port, like localhost:5055/myorg/myimage, now gets :latest in the Destination image: line, because the tag check only looks after the last / and no longer mistakes the port for a tag. The pushed image is the same as before, and Docker Hub destinations such as myorg/myimage print exactly what they used to.

• [#72] Added 'SANITIZE_PROCEED' and 'SANITIZE_FILE' to 'seed.sh' to sanitize the database before it is captured. @AlexSkrypnyk (#214)
  Set SANITIZE_PROCEED=1 and seed.sh runs the queries from SANITIZE_FILE (by default ./scripts/sanitize.sql, where Vortex projects keep theirs) before it captures the database, so the data they remove or replace never reaches the image; any value other than 1 leaves it off. The queries run in a throwaway container and the image comes from a fresh container that imports its export, at the cost of a second import, because sanitizing in place would leave the originals in the InnoDB redo log that's captured with the data files. A failing query, or a dump or query that changes accounts, grants or other mysql system tables, stops seeding before anything is pushed, and any failed run, sanitizing or not, now removes the container it was running instead of leaving it up, keeping its logs.

• [#210] Added 'MARIADB_FORCE_UPGRADE' with 'FORCE_MYSQL_UPGRADE' as a deprecated alias and fixed Renovate missing the 'ci-runner' image. @AlexSkrypnyk (#213)
  The image now takes MARIADB_FORCE_UPGRADE=1 to run mariadb-upgrade --force when it starts on an existing data directory, in line with the MARIADB_ prefix every other setting uses. FORCE_MYSQL_UPGRADE=1 still works but logs a deprecation notice, and a non-empty MARIADB_FORCE_UPGRADE always wins, so MARIADB_FORCE_UPGRADE=0 keeps the upgrade off even when the old name is 1. The Renovate part only touches CI: the drevops/ci-runner image in the test matrix was invisible to Renovate and now gets update PRs.

• [#209] Renamed 'DST_IMAGE' to 'DESTINATION_IMAGE' in 'seed.sh' with a deprecated alias. @AlexSkrypnyk (#212)
  seed.sh now reads the destination image from DESTINATION_IMAGE, spelled the same way as DESTINATION_PLATFORMS, ahead of DST_IMAGE and then the second argument. DST_IMAGE keeps working but prints a deprecation notice, so it's worth switching to the new name. The same PR fixes 2 rough edges: a run with no destination now prints the proper must be provided error instead of 2: unbound variable, and a run that fails before any container starts, such as a failed base image pull, puts .dockerignore back instead of leaving it as .dockerignore.bak.

• Unified code conventions and fixed 'seed.sh', entrypoint and test-suite defects. @AlexSkrypnyk (#211)
  2 seedings started from the same BASE_IMAGE on a shared Docker host can no longer import into or stop each other's container: seed.sh now tracks the ID that docker run -d returns instead of taking the first match from docker ps --filter ancestor=..., and a successful run removes its 2 containers and their volumes instead of leaving them stopped. In the image, the entrypoint recreates a missing .my.cnf in the data directory rather than in /var/lib/mysql, so an image whose data directory lacks the file now gets the password-less mysql login with its default database, while images seeded by seed.sh already carry it and see no change. Missing system tables now print [FAIL] instead of a green [ OK ], and the rest of the PR is convention, CI and test-suite cleanup.

Other changes

• [#208] Fixed scaffold docs and config drift. @AlexSkrypnyk (#212)
  None of this changes how the image or seed.sh behave: the contributor docs and agent config inherited from the scaffold template (the template this repository is generated from) disagreed with CI and with each other, and CONTRIBUTING.md and AGENTS.md now match the commands CI runs. A coverage marker kcov doesn't recognise (LCOV_EXCL_END instead of LCOV_EXCL_STOP) had also excluded most of tests/bats/_helper.bash from coverage, and those lines are counted again.

• Updated scaffold to 1.3.0. @AlexSkrypnyk (#207)
  This syncs the repository with version 1.3.0 of the scaffold template, which touches CI, docs and repository config but not the image or seed.sh. Tag pushes now run release-docker.yml, which publishes the same image tags and seed.sh release asset as before, so the releases/latest/download/seed.sh link keeps resolving, and the duplicate workflows that drafted release notes and assigned PR authors 2 times per event are gone.

• chore(deps): update release-drafter/release-drafter digest to 72967cd @renovate[bot] (#206)

• chore(deps): update release-drafter/release-drafter digest to c345907 @renovate[bot] (#205)

• chore(deps): update uselagoon/mariadb-10.11-drupal docker tag to v26.9.0 @renovate[bot] (#204)

• chore(deps): update codecov/codecov-action digest to 303a32d @renovate[bot] (#203)

• chore(deps): update docker/setup-buildx-action digest to f87e599 @renovate[bot] (#202)

• chore(deps): update all dependencies @renovate[bot] (#201)

• chore(deps): update codecov/codecov-action digest to 0b35c9e @renovate[bot] (#200)

• chore(deps): update docker/setup-qemu-action digest to 1f40c72 @renovate[bot] (#199)

• chore(deps): update softprops/action-gh-release digest to efb3536 @renovate[bot] (#198)

• chore(deps): update uselagoon/mariadb-10.11-drupal docker tag to v26.8.1 @renovate[bot] (#197)

• chore(deps): update docker/setup-buildx-action digest to 37fe631 @renovate[bot] (#196)

Full Changelog: 26.8.1...26.10.0