release: prepare mb3r-stack v0.3.3

Author: a-a-k

README.md

@@ -3,8 +3,8 @@
 [![Release](https://img.shields.io/github/v/release/MB3R-Lab/mb3r-stack)](https://github.com/MB3R-Lab/mb3r-stack/releases)
 [![release](https://img.shields.io/github/actions/workflow/status/MB3R-Lab/mb3r-stack/release.yml?label=release)](https://github.com/MB3R-Lab/mb3r-stack/actions/workflows/release.yml)
 [![ci](https://img.shields.io/github/actions/workflow/status/MB3R-Lab/mb3r-stack/ci.yml?branch=main&label=ci)](https://github.com/MB3R-Lab/mb3r-stack/actions/workflows/ci.yml)
-[![Candidate bundle](https://img.shields.io/badge/candidate-v0.3.2-orange)](https://github.com/MB3R-Lab/mb3r-stack/releases/tag/v0.3.2)
-[![Upstream pins](https://img.shields.io/badge/Bering%20%7C%20Sheaft-0.3.2%20%7C%200.2.3-blue)](https://github.com/MB3R-Lab/mb3r-stack/blob/main/compat/stack-manifest.json)
+[![Candidate bundle](https://img.shields.io/badge/candidate-v0.3.3-orange)](https://github.com/MB3R-Lab/mb3r-stack/releases/tag/v0.3.3)
+[![Upstream pins](https://img.shields.io/badge/Bering%20%7C%20Sheaft-0.3.3%20%7C%200.2.3-blue)](https://github.com/MB3R-Lab/mb3r-stack/blob/main/compat/stack-manifest.json)
 [![Adapter contracts](https://img.shields.io/badge/adapter_contracts-v1alpha1-blue)](https://github.com/MB3R-Lab/mb3r-stack/blob/main/compat/compatibility-matrix.json)
 
 `mb3r-stack` is the MB3R integration and distribution repository.
@@ -38,12 +38,12 @@ A stack release publishes:
 - application business logic
 - the canonical release cadence of upstream Bering or Sheaft artifacts
 
-Current bundle candidate pins published upstream artifacts explicitly: Bering `0.3.2` and Sheaft `0.2.3`, including immutable image digests and contract evidence in `compat/`.
+Current bundle candidate pins published upstream artifacts explicitly: Bering `0.3.3` and Sheaft `0.2.3`, including immutable image digests and contract evidence in `compat/`.
 
-Current packaged release assets for `v0.3.2` are:
+Current packaged release assets for `v0.3.3` are:
 
-- `dist/charts/mb3r-stack-0.3.2.tgz`
-- `dist/assets/mb3r-assets-0.3.2.tgz`
+- `dist/charts/mb3r-stack-0.3.3.tgz`
+- `dist/assets/mb3r-assets-0.3.3.tgz`
 - `dist/release-manifest.json`
 - `dist/SHA256SUMS.txt`
 - `dist/sbom.cdx.json`
@@ -105,7 +105,7 @@ python scripts/tasks.py release-dry-run
 
 ## Compatibility Notes
 
-The compatibility files in `compat/` are the source of truth for stack-level assertions. The current `0.3.2` bundle is recorded as a `candidate` integration statement backed by upstream release manifests, repository validation, release dry-run, adapter e2e, and Sheaft's published compatibility manifest, not as a broader verified operations guarantee. OpenTelemetry Demo remains one example profile and one acceptance scenario, not the design center of the core bundle.
+The compatibility files in `compat/` are the source of truth for stack-level assertions. The current `0.3.3` bundle is recorded as a `candidate` integration statement backed by upstream release manifests, repository validation, release dry-run, adapter e2e, and Sheaft's published compatibility manifest, not as a broader verified operations guarantee. OpenTelemetry Demo remains one example profile and one acceptance scenario, not the design center of the core bundle.
 
 ## License
 

VERSIONING.md

@@ -36,6 +36,6 @@ If a pin is unknown, keep it explicit with `TODO-*` placeholders and mark the co
 
 ## Tagging
 
-Repository tags should use `v<semver>`, for example `v0.3.2`.
+Repository tags should use `v<semver>`, for example `v0.3.3`.
 
 The current bundle line is still pre-GA integration packaging and remains conservative about formal maturity even as validation depth increases.

charts/mb3r-stack/Chart.yaml

@@ -2,8 +2,8 @@ apiVersion: v2
 name: mb3r-stack
 description: Generic integration bundle that wires upstream Bering and Sheaft into OTLP-based or artifact-based Kubernetes environments.
 type: application
-version: 0.3.2
-appVersion: "0.3.2"
+version: 0.3.3
+appVersion: "0.3.3"
 keywords:
   - mb3r
   - otlp

charts/mb3r-stack/values.yaml

@@ -39,8 +39,8 @@ bering:
   image:
     registry: ""
     repository: "ghcr.io/mb3r-lab/bering"
-    tag: "v0.3.2"
-    digest: "sha256:98e443461bf59d92cc19b20f425602de91b22a272ecd9a79df5cc20f96c735a8"
+    tag: "v0.3.3"
+    digest: "sha256:b38713a15194827f3410c3972071a5fd358f1fe55847952289f5edd7c0b82174"
     pullPolicy: IfNotPresent
   podLabels: {}
   podAnnotations: {}

compat/compatibility-matrix.json

@@ -3,6 +3,30 @@
   "schemaVersion": "1.0.0",
   "generatedAt": "2026-05-01",
   "entries": [
+    {
+      "stackVersion": "0.3.3",
+      "beringVersion": "0.3.3",
+      "sheaftVersion": "0.2.3",
+      "chartVersion": "0.3.3",
+      "compatibilityState": "candidate",
+      "evidence": "Pinned to https://github.com/MB3R-Lab/Bering/releases/download/v0.3.3/release-manifest.json plus https://github.com/MB3R-Lab/Bering/releases/download/v0.3.3/contracts-manifest.json and https://github.com/MB3R-Lab/Sheaft/releases/download/v0.2.3/release-manifest.json and https://github.com/MB3R-Lab/Sheaft/releases/download/v0.2.3/compatibility-manifest.json; verified by repository validate, adapter e2e, release dry-run, Helm template render checks, and live kind-based generic smoke with pinned GHCR images on 2026-05-01.",
+      "contracts": {
+        "collectorExport": "v1alpha1",
+        "discoveryReport": "v1alpha1",
+        "gateDecision": "v1alpha1",
+        "reportPayload": "v1alpha1"
+      },
+      "dashboards": {
+        "bering": "1.0.0",
+        "sheaft": "1.0.0"
+      },
+      "notes": [
+        "Bering v0.3.3 publishes the same io.mb3r.bering.model and io.mb3r.bering.snapshot schema lines for both 1.0.0 and 1.1.0, and Sheaft v0.2.3 strictly accepts both lines.",
+        "Bering v0.3.3 is a release metadata hygiene patch with no declared schema, CLI, API, or install-surface break.",
+        "Sheaft v0.2.3 fixes serve/watch startup when the Bering latest artifact appears after Sheaft starts.",
+        "This remains a candidate integration statement rather than a GA support claim."
+      ]
+    },
     {
       "stackVersion": "0.3.2",
       "beringVersion": "0.3.2",

compat/stack-manifest.json

@@ -3,28 +3,28 @@
   "schemaVersion": "1.0.0",
   "stack": {
     "name": "mb3r-stack",
-    "version": "0.3.2",
+    "version": "0.3.3",
     "status": "candidate",
     "releaseDate": "2026-05-01",
     "notes": [
       "Generic integration and distribution layer only. No upstream Bering or Sheaft source code is vendored here.",
-      "Candidate bundle pinned to released Bering v0.3.2 and Sheaft v0.2.3 artifacts with immutable GHCR digests.",
+      "Candidate bundle pinned to released Bering v0.3.3 and Sheaft v0.2.3 artifacts with immutable GHCR digests.",
       "OpenTelemetry Demo is packaged as an example profile, not as the core contract.",
-      "Bering v0.3.2 keeps the published 1.0.0 and 1.1.0 schema contract lines while adding runtime and toolchain hardening.",
+      "Bering v0.3.3 keeps the published 1.0.0 and 1.1.0 schema contract lines and refreshes release-facing metadata.",
       "Sheaft v0.2.3 strictly validates both the 1.0.0 and 1.1.0 Bering schema lines and fixes late Bering artifact handoff in serve/watch preview mode.",
       "Pinned GHCR images are recorded from the upstream release manifests published on 2026-05-01."
     ]
   },
   "artifacts": {
     "chart": {
       "name": "mb3r-stack",
-      "version": "0.3.2",
+      "version": "0.3.3",
       "ociRepository": "oci://ghcr.io/mb3r-lab/charts",
-      "package": "mb3r-stack-0.3.2.tgz"
+      "package": "mb3r-stack-0.3.3.tgz"
     },
     "assetPack": {
-      "version": "0.3.2",
-      "archive": "mb3r-assets-0.3.2.tgz",
+      "version": "0.3.3",
+      "archive": "mb3r-assets-0.3.3.tgz",
       "includes": [
         "collector/",
         "dashboards/",
@@ -36,17 +36,17 @@
       "sheaft": "1.0.0"
     },
     "configPacks": {
-      "collector": "0.3.2",
-      "examples": "0.3.2"
+      "collector": "0.3.3",
+      "examples": "0.3.3"
     }
   },
   "components": {
     "bering": {
-      "version": "0.3.2",
+      "version": "0.3.3",
       "image": {
         "repository": "ghcr.io/mb3r-lab/bering",
-        "tag": "v0.3.2",
-        "digest": "sha256:98e443461bf59d92cc19b20f425602de91b22a272ecd9a79df5cc20f96c735a8"
+        "tag": "v0.3.3",
+        "digest": "sha256:b38713a15194827f3410c3972071a5fd358f1fe55847952289f5edd7c0b82174"
       },
       "contracts": {
         "collectorExport": "v1alpha1",

docs/compatibility.md

@@ -41,9 +41,9 @@ OpenTelemetry Demo can be part of the evidence set, but it is not sufficient by
 
 ## Current Bundle
 
-`mb3r-stack` `0.3.2` currently tracks:
+`mb3r-stack` `0.3.3` currently tracks:
 
-- Bering `0.3.2`
+- Bering `0.3.3`
 - Sheaft `0.2.3`
 
 That bundle is marked `candidate` because the pins are backed by published upstream release metadata and strict contract alignment, while broader operational verification remains outside this repository's release contract. The current upstream pairing keeps the stack-level adapter envelopes on `v1alpha1` while aligning the Bering-to-Sheaft artifact handoff on the published `io.mb3r.bering.model` and `io.mb3r.bering.snapshot` schema lines for both `1.0.0` and `1.1.0`. That still does not change the formal maturity of the bundle or the upstream preview status of Sheaft `serve` behavior.

docs/getting-started.md

@@ -38,10 +38,10 @@ For first-time evaluation, use this sequence:
 
 The expected product outcome is a visible Bering -> Sheaft handoff and a Sheaft posture report. The OTel Demo profile is a showcase path, not the first proof of generic readiness.
 
-The current packaged bundle line is `v0.3.2`, which stages these release assets during `make release-dry-run`:
+The current packaged bundle line is `v0.3.3`, which stages these release assets during `make release-dry-run`:
 
-- `dist/charts/mb3r-stack-0.3.2.tgz`
-- `dist/assets/mb3r-assets-0.3.2.tgz`
+- `dist/charts/mb3r-stack-0.3.3.tgz`
+- `dist/assets/mb3r-assets-0.3.3.tgz`
 - `dist/release-manifest.json`
 
 ## Next Steps

docs/install-gitlab.md

@@ -22,7 +22,7 @@ Use component references pinned by tag, for example:
 
 ```yaml
 include:
-  - component: $CI_SERVER_FQDN/group/mb3r-stack/bering-discover@v0.3.2
+  - component: $CI_SERVER_FQDN/group/mb3r-stack/bering-discover@v0.3.3
 ```
 
 Keep the tag aligned with the `mb3r-stack` integration bundle release, not with any upstream Bering or Sheaft release number.

docs/install-jenkins.md

@@ -21,5 +21,5 @@ See `examples/jenkins/Jenkinsfile`.
 Use the library by tag:
 
 ```groovy
-@Library('mb3r-stack@v0.3.2') _
+@Library('mb3r-stack@v0.3.3') _
 ```