You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by ha...@apache.org on 2026/09/16 06:09:43 UTC

(skywalking-banyandb) branch v0.11.x updated: chore(release): keep path-safe name allowlist under 0.11.1

This is an automated email from the ASF dual-hosted git repository.

hanahmily pushed a commit to branch v0.11.x
in repository https://gitbox.apache.org/repos/asf/skywalking-banyandb.git


The following commit(s) were added to refs/heads/v0.11.x by this push:
     new 330bd4e33 chore(release): keep path-safe name allowlist under 0.11.1
330bd4e33 is described below

commit 330bd4e339c09b5ace889625da6d1e1f772be6e3
Author: Gao Hongtao <ha...@gmail.com>
AuthorDate: Wed Sep 16 06:09:37 2026 +0000

    chore(release): keep path-safe name allowlist under 0.11.1
    
    0.11.1 is unreleased, so every change after 0.11.0 belongs there.
    
    Co-authored-by: Cursor <cu...@cursor.com>
---
 CHANGES.md | 17 ++++++-----------
 1 file changed, 6 insertions(+), 11 deletions(-)

diff --git a/CHANGES.md b/CHANGES.md
index a543db753..0dc76a4f4 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -2,17 +2,6 @@
 
 Release Notes.
 
-## 0.11.2
-
-### Bug Fixes
-
-- Reject group / stream / measure / trace (and related) resource names that are not a single path-safe identifier (`[a-zA-Z0-9_]([a-zA-Z0-9._-]*[a-zA-Z0-9])?`), so names cannot escape catalog storage roots.
-- Bound protobuf `validate.rules` on schema and query identifiers (max length, allowlist pattern, repeated max_items, numeric ceilings) so untrusted inputs cannot escape storage roots or force unbounded allocations.
-
-### Chores
-
-- Bump google.golang.org/grpc to v1.83.2 to clear GO-2026-6443, GO-2026-6441, and GO-2026-6348.
-
 ## 0.11.1
 
 ### Bug Fixes
@@ -30,6 +19,12 @@ Release Notes.
 - Register the memory protector on the liaison role so query admission uses the cgroup-backed pool instead of the 64MiB fallback.
 - Reject deeply nested ByDBQL WHERE parentheses to prevent stack overflow.
 - Keep system native `memory_state` (with `kind` labels) from being overwritten by the liaison load-shedding gauge so self-observability dashboard queries succeed.
+- Reject group / stream / measure / trace (and related) resource names that are not a single path-safe identifier (`[a-zA-Z0-9_]([a-zA-Z0-9._-]*[a-zA-Z0-9])?`), so names cannot escape catalog storage roots.
+- Bound protobuf `validate.rules` on schema and query identifiers (max length, allowlist pattern, repeated max_items, numeric ceilings) so untrusted inputs cannot escape storage roots or force unbounded allocations.
+
+### Chores
+
+- Bump google.golang.org/grpc to v1.83.2 to clear GO-2026-6443, GO-2026-6441, and GO-2026-6348.
 
 ## 0.11.0