Skip to content

release: v1.34.0-beta.2 - #1626

Merged
geodro merged 3 commits into
mainfrom
release/v1.34.0-beta.2
Aug 31, 2026
Merged

release: v1.34.0-beta.2#1626
geodro merged 3 commits into
mainfrom
release/v1.34.0-beta.2

Conversation

@geodro

@geodro geodro commented Aug 31, 2026

Copy link
Copy Markdown
Member

Second beta of the 1.34.0 line, fix-only. The beta heading is replaced in place rather than opened above the first, so the changelog section still describes the whole line and gains what the last week added to it.

The extension clobber is the one that reached a user. Fixing ext/ftp in the published base image only made it visible how completely a declared custom extension replaced the image's own build of the same name, so ftp lost FTPS again the moment someone had declared it. Builds skip a bundled name now, php:ext add refuses one, and an image built while a declaration was still replacing the better build reads as out of date once so it heals itself.

The macOS side covers four defects that shared a root: a guard that never fired let a test run rearrange the developer's own launchd, unit removal left the job registered against a plist it had deleted, three installer checks could not run there at all, and domain add doubled a name that already carried the TLD.

The DOMPurify pin moves past the advisory in the copy monaco-editor pulls into the dashboard. The configuration the advisory needs is not one the dashboard uses, so no shipped build was exploitable, but the vulnerable code is out of the bundle.

The README needs nothing: this beta adds no surface it describes, and the AI reference was updated by each change as it landed.

Second beta of the 1.34.0 line, and it is a fix-only one. The beta heading is replaced in place rather than opened above the first, so the section still describes the whole line and gains what the last week added to it.

The extension clobber is the one that reached a user. Fixing ext/ftp in the published base image only made it visible how completely a declared custom extension replaced the image's own build of the same name, so ftp lost FTPS again the moment someone had declared it. Builds skip a bundled name now, php:ext add refuses one, and an image built while a declaration was still replacing the better build reads as out of date once so it heals itself.

The macOS side covers four defects that shared a root: a guard that never fired let a test run rearrange the developer's own launchd, unit removal left the job registered against a plist it had deleted, three installer checks could not run there at all, and domain add doubled a name that already carried the TLD.

The DOMPurify pin moves past the advisory in the copy monaco-editor pulls into the dashboard. The configuration the advisory needs is not one the dashboard uses, so no shipped build was exploitable, but the vulnerable code is out of the bundle.

The README needs nothing: this beta adds no surface it describes, and the AI reference was updated by each change as it landed.
@geodro
geodro requested a review from a team as a code owner August 31, 2026 14:47
geodro added 2 commits August 31, 2026 18:21
The declared worker set landed after the release branch was cut, and it is the half of #1531 the reporter was still seeing, so it belongs in the same beta rather than the next one.
@geodro
geodro merged commit f09a9ec into main Aug 31, 2026
6 checks passed
@geodro
geodro deleted the release/v1.34.0-beta.2 branch August 31, 2026 15:26
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.

1 participant