Tags give the ability to mark specific points in history as being important
-
v0.11.0
cf0a08f2 · ·v0.11.0: SubclusterService.AdoptSubcluster (register-unified-tahr, protos !18) Additive minor: new proto/vibecluster/v1alpha/subcluster.proto with SubclusterService.AdoptSubcluster + AdoptSubclusterRequest/Response + BastionEndpoint, Go + TS generated code, package.json exports subpath. buf breaking vs v0.10.0 CLEAN. Public-repo scrub verified (protos !18).
-
v0.10.0
d68179ad · ·v0.10.0 — ChunkType taxonomy for non-cluster honeycomb chunks Additive, non-breaking. Adds 11 values to ChunkType (2-12) so canvases other than the federated-clusters view can persist per-user honeycomb positions: NAV_ITEM=2, RESOURCE_CATEGORY=3, POD=4, NODE=5, DEPLOYMENT=6, NAMESPACE=7, SERVICE=8, CONFIG_MAP=9, SECRET=10, VOLUME=11, VM=12 Before this, UpdateChunkPositionRequest.chunk_type enforced defined_only + not_in:[0] against a two-value enum, so only cluster chunks could be positioned at all. Enum-only: no message, field, RPC, or validation rule changed, and values 0 and 1 are untouched. buf breaking against v0.9.0 reports no breaking changes. chunk_id contracts are documented per value. Note VOLUME deliberately covers both claim and volume objects because they share one canvas, distinguished by the persisted key prefixes "pvc:<namespace>/<name>" and "pv:<name>". Placement is a convention, not a schema invariant: CLUSTER and NAV_ITEM sit in the root view, the rest are currently nested under (CLUSTER, <cluster name>), but the parent fields accept any defined type so a type may later be nested elsewhere without a schema change.
-
v0.9.0
29877228 · ·v0.9.0 — view-scoped chunk positions Additive (minor): adds parent_chunk_type + parent_chunk_id to UpdateChunkPositionRequest and GetChunkPositionsRequest so chunk positions are scoped per view (view = the parent chunk navigated into; root view = CHUNK_TYPE_UNSPECIFIED + empty id). A read returns only the requested view's positions. Optional chunk_type filter retained (applies within the view). No breaking changes. Merged via !16 (register-view-scoped-positions).
-
v0.8.0
e1971826 · ·v0.8.0 — GetChunkPositions read RPC (chunk-position read-back) Additive (minor): adds ChunkService.GetChunkPositions returning the calling user's saved ChunkPosition{chunk_type, chunk_id, position} list (optional chunk_type filter; identity server-derived). Completes the write/read pair with v0.7.0's UpdateChunkPosition. Reuses ChunkType + HexPosition. No breaking changes. Merged via !15 (register-chunk-position-read). -
v0.7.0
e90424ec · ·v0.7.0 — generic ChunkService + UpdateChunkPosition (chunk_type enum) BREAKING (pre-1.0 minor): replaces ClusterService with a generic ChunkService; adds UpdateChunkPosition(ChunkType chunk_type, string chunk_id, HexPosition); removes UpdateClusterPosition + Cluster.position (field 8 reserved). ChunkType is a code-shipped enum (CHUNK_TYPE_UNSPECIFIED=0, CHUNK_TYPE_CLUSTER=1). Cluster/ListClusters/GetCluster unchanged. Regenerated Go + TS. Merged via !14 (register-generic-chunk-position).
-
v0.6.0
9a9b7f38 · ·v0.6.0 — HexPosition, Cluster.position (field 8), UpdateClusterPosition RPC Adds proto foundation for per-user server-side cluster position persistence (honeycomb-drag-snap). Additive: new HexPosition message, Cluster.position field 8, UpdateClusterPosition RPC on ClusterService. Regenerated Go + TS. Merged via !13 (register-allowing-hagfish).
-
-
-
-
-
v0.1.1
b13e80dd · ·feat: add ToolInvocation streaming event to ChatResponse Adds ToolInvocation message with 6 fields (tool_name, arguments_json, result_summary, cluster_name, elapsed_ms, success) as a third oneof event variant in ChatResponse for real-time tool execution transparency.
-
v0.1.0-rc2
2e6f6440 · ·rc2: move to gitlab.com/aranya-tech/protos canonical URL; Go module path updated