Release notes: Platform Update 26.7 - #25
Draft
nl0 wants to merge 1 commit into
Draft
Conversation
Security- and reliability-focused release, plus the switch to date-based version numbering (1.71 -> 26.7). Grouped by theme from the [26.7.0] CHANGELOG section on the deployment rc branch. Called out deliberately: - The Catalog soft-delete change, including the managed-role permission consequence: read-write roles no longer grant s3:DeleteObjectVersion, so permanent version deletion (including via quilt3) now needs an admin custom policy. - A note explaining that date-based numbering is a change in what the numbers mean, not a 25-major-version jump, and that existing minimum-version statements in the docs still read correctly. Internal engineering items (CI, telemetry, template refactors, the Terraform provider lock) are intentionally excluded.
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
1 participant
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.
Release notes for Quilt Platform 26.7 (tag
26.7.0), to merge once the release ships.Source: the
[26.7.0]section oft4/CHANGELOG.mdon thercbranch of quiltdata/deployment. Release tracked inqhq-lf0a; rc is baking at https://rc.quilttest.com (stackVersion 26.7.0-rc-2-g8ab943b1).Shape of this release
Predominantly security and reliability. The user-visible surface is thin, and the notes say so rather than inflating it: three Platform-level changes, one large batch of security-scanner hardening presented as such, and two operational fixes.
Two things worth reviewing closely
The version-numbering note. This is the first release under date-based numbering (
YY.M.PATCH) — 1.71 to 26.7. The note states that this changes what the numbers mean rather than the platform, that it is not a twenty-five-major-version jump, and that existing "requires 1.70.0 or higher" statements in the docs still read correctly since 26.7 is later than any 1.x. Worth a second opinion on the framing, since this is the first time customers see it.The soft-delete permission consequence. Beyond the delete-marker behavior, managed read-write roles no longer grant
s3:DeleteObjectVersion. Anyone who relied on a managed read-write role to permanently delete object versions — including throughquilt3— will now getAccessDenieduntil an admin grants the action via a custom policy. That is a real behavioral regression for those users, so it is stated explicitly rather than buried. The wording is grounded in the docs that shipped with the code change (docs/FAQ.md,docs/advanced-features/s3-prefix-permissions.mdin quilt#5161), not paraphrased from the CHANGELOG.Deliberate exclusions
Internal engineering items are left out: the Checkov CI gate, stack-monitoring telemetry, the
make_assumable_rolerefactor, the NAT-gateway EIP literal, and the Terraform provider lock files. Also excluded: Grok being added toConnectAllowedHosts, which landed for internal stacks only (nightly,open-quilt-bio,auto-stack-dev) — documenting it would amount to declaring Grok a supported client, which is a product call, not a release-notes one.🤖 Generated with Claude Code