Repository navigation
chore: release prep for 2.4.2 - #816
Merged
Merged
Conversation
Sixteen PRs merged since the 2.4.1 tag; [Unreleased] documented three of them and none of the five advisory fixes. A security release whose notes omit its security fixes gives nobody a reason to upgrade, which is the operator-facing half of the failure SECURITY.md triage exists to prevent. Renames [Unreleased] to 2.4.2 and documents all of it: - Security: the six advisories closed (#814, #799, #798, #796 x2, #815) and the three reachable dependency advisories (#797, #807, #811), plus the Go 1.27 builder (#800). - Fixed: the audit-filter parity bugs (#802) and the Cassandra index probe that never waited (#810). - Changed: direct-gRPC x-authorizer-url now yields to --url (#814), and the dropped Cassandra audit_log(created_at) index (#812). - Added: the audit plumbing (#806), stated as writing no new records and changing no behaviour, plus two deployment entries. - Upgrade notes: eight items, including the three that were missing entirely — that ANY two audit filters now scan on Cassandra (not only the timestamp range, which the previous note implied), the longer first start on ScyllaDB now that probes genuinely block, and the manual DROP INDEX for the removed index. Section order leads with Security, matching 2.4.1 — the file orders by what matters for the release at hand rather than a fixed sequence. Deliberately omitted: #791 (scorecard action bump) and #809 (the previous changelog edit). Neither is user-facing; Keep a Changelog asks for notable changes, not a commit log. The ScyllaDB view-build note is scoped to ScyllaDB: global secondary indexes are materialized views there, while Apache Cassandra builds local 2i with no view-build step and no nodetool viewbuildstatus.
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.
Release prep for 2.4.2. Renames
[Unreleased]to2.4.2and documents everything in it.Why this is more than a rename
Sixteen PRs have merged since the 2.4.1 tag.
[Unreleased]documented three of them, and none of the five advisory fixes. A security release whose notes omit its own security fixes gives nobody a reason to upgrade — which is the operator-facing half of exactly the failure theSECURITY.mdtriage process exists to prevent.Contents
Security — the six advisories now closed, and the three reachable dependency advisories:
/verify_emaildelivered tokens in the query stringvalidate_jwt_tokendid not bind the signedtoken_type/authorize/consentaccepted a delegated tokenPlus gRPC v1.83.2 (#797), OpenTelemetry v1.45.0 (#807),
golang.org/x/netv0.60.0 (#811), and the Go 1.27 builder (#800). Each states why it was reachable here, not just that it was bumped — including the gRPC version subtlety, where the advisory names v1.82.2 as the fix but on the 1.83.x line it landed in v1.83.2, so v1.83.1 is still affected.Fixed — the audit-filter parity bugs (#802) and the Cassandra index probe that never waited (#810).
Changed — direct-gRPC
x-authorizer-urlnow yields to--url(#814), and the dropped Cassandraaudit_log(created_at)index (#812).Added — the audit plumbing (#806), stated explicitly as writing no new records and changing no behaviour so nobody reads it as a live feature, plus the two deployment entries (#801, #808).
Upgrade notes — three of these did not exist before
The previously-written notes were incomplete in ways an operator would have discovered in production:
ALLOW FILTERINGfor any second restriction — one query can be served by one index._audit_logs(action:, actor_id:)is an ordinary admin search and it now scans. Still better than the pre-2.4.2 behaviour, where that exact combination errored outright on ScyllaDB.DROP INDEXfor the removedaudit_log(created_at)index, with the CQL. Existing deployments keep the index until dropped; nothing breaks if left.The ScyllaDB view-build note is now scoped to ScyllaDB specifically: global secondary indexes are materialized views there, whereas Apache Cassandra builds local 2i with no view-build step and no
nodetool viewbuildstatus. The previous wording was headed "CassandraDB/ScyllaDB" and would have sent Cassandra operators looking for a command that does not apply.Decisions worth noting
CHANGELOG.mdonly — the image tag comes from the release.Verification
The release candidate was re-verified before this was written, on
b5012cbc:Backend coverage was confirmed explicitly rather than inferred from a failure count — postgres, sqlite, mongodb, arangodb, scylladb, dynamodb, couchbase, each running the full 9-case audit-log group, with
TestNotFoundContractIsUniformandTestDeleteUserCascadeIsUniformboth passing.Docs-only change, so no code risk here; the entries were written from each commit's own body rather than from the PR titles.