Release v2026.2#1835
Draft
matthew-white wants to merge 63 commits into
Draft
Conversation
Previously called `disallow-all`; rename to `backend-strict` to better reflect its usage rather than current implementation details.
Looks like a merge error.
Switch from Content-Security-Policy-Report-Only to Content-Security-Policy.
Switch from Content-Security-Policy-Report-Only to Content-Security-Policy.
It looks like the checkout code from the `test-images` job was copy/pasted elsewhere. Simplifying this config should speed up git checkout in affected jobs.
Fixes: expected docker context is increased due to WF merge
Fixes/install openssl
The `DB_SSL` env var was made illegal in #1647. The check was then moved from runtime to build time in #1671. Checking at build-time allows for faster failure and clearer feedback to sysadmins who are upgrading, and previously depended on this env var. However, the downside is that if container images are pre-built centrally, this check will be skipped. With this commit, the check will move to container startup. However, it will now be skipped if the container is started with a non-standard CMD/command/COMMAND.
Switch all headers from `Content-Security-Policy-Report-Only` to `Content-Security-Policy`.
Restrict TCP ports to the local machine. This will prevent exposing these dev services on the local network or wider.
Tests pass with nginx: ✅ `1.29.7` Tests fail with nginx: ☠️ `1.29.5` ☠️ `1.29.6` Closes #1736
Restrict TCP ports to the local machine. This will prevent exposing these dev services on the local network or wider.
Increase the lower and upper bounds to: * take account of larger contexts in forked repositories, and * tighten the acceptable margin
One less place to keep up-to-date.
Reduces max-old-space-size allocation by 2GB (50%). On dev.getodk.cloud this currently: * fails with 1024 * passes with 1536 This suggests decreasing to 2048 is: 1. a good saving, and 2. fairly safe
Use no longer encouraged. Closes #1894
Instead of changing the global builder default, just use the `docker_context_checker` custom builder for the specific job it was written for. This is helpful for dev machines so that other docker jobs are not affected by this script.
The linked PR is very long, and doesn't give clear guidance/explanation of what's going on. Ultimately this test should be the source of truth for the paths which serve web-forms content, and more context can be added here if required.
Newer versions have been released but less than 14 days ago. None of the high priority CVEs fixed affect us.
It was released only a week ago but it fixes additional buffer overread and overflow issues over 1.31.1 released a month ago.
2.0.0 was released 3 weeks ago and followed up with point releases. Let's wait until it stabilizes, we don't need any of the udpates.
8.8 has been out a month but it makes some significant changes so I'd rather be conservative
Update infrastructure dependencies for v2026.2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR prepares the release of v2026.2. It should only contain changes from other PRs that have already been approved and merged (and possibly merge commits from the
masterbranch).