Skip to content

Release v2026.4.0 - #2254

Draft
matthew-white wants to merge 5 commits into
masterfrom
next
Draft

matthew-white wants to merge 5 commits into
masterfrom
next

Conversation

@matthew-white

Copy link
Copy Markdown
Member

This PR prepares the release of v2026.4. It should only contain changes from other PRs that have already been approved and merged (and possibly merge commits from the master branch).

alxndrsn and others added 5 commits September 17, 2026 11:20
…2248)

This seems to prevent a race condition related to volume creation order:

	Container central-postgres14-1  Error response from daemon: failed to mkdir /var/lib/docker/volumes/central_postgres14/_data/data: mkdir /var/lib/docker/volumes/central_postgres14/_data/data: file exists

This error was seen ~3% of the time when running:

* `postgres` container based on `tianon/postgres-upgrade:9.6-to-14`
* `postgres14` container based on `pgautoupgrade/pgautoupgrade:17.11-trixie`

Given the vague nature of both the error itself, and reproduction circumstances, it seems prudent to introduce this dependency.

The dependency itself seems logical, as the `postgres14` container should be waiting for the `postgres` container to create a flag file before PostgreSQL itself starts up.

See:

* moby/moby#47021
* https://forums.docker.com/t/error-while-creating-mount-source-path-after-docker-desktop-update-to-v4-35/144676
In the original implementation (#343), old postgres data was cleaned up automatically if a specific flag file was present.

This behaviour was changed (prior to release?) in a follow-up PR (#395) to link to documentation instead.

Over time, it's become less clear which part of the linked documentation is relevant.  This PR aims to link more directly to the relevant documentation.
For legacy reasons, some `npm` commands were being invoked in `./test/nginx` instead of `./test`.  This works because `npm` looks for the nearest `package.json` file and uses its directory as PWD.  But also quite confusing, especially in the case of `npm run test:service`, which has nothing to do with the code in `test/nginx`.

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