Bump bundle metadata to v0.2.2

Author: a-a-k

README.md

@@ -90,7 +90,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.2.1` bundle is recorded as a `candidate` integration statement backed by upstream release manifests, live generic smoke evidence, 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.2.2` bundle is recorded as a `candidate` integration statement backed by upstream release manifests, live generic smoke evidence, 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.2.1`.
+Repository tags should use `v<semver>`, for example `v0.2.2`.
 
 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.2.1
-appVersion: "0.2.1"
+version: 0.2.2
+appVersion: "0.2.2"
 keywords:
   - mb3r
   - otlp

compat/compatibility-matrix.json

@@ -1,8 +1,31 @@
 {
   "$schema": "../schemas/compatibility-matrix.schema.json",
   "schemaVersion": "1.0.0",
-  "generatedAt": "2026-03-15",
+  "generatedAt": "2026-03-16",
   "entries": [
+    {
+      "stackVersion": "0.2.2",
+      "beringVersion": "0.1.0",
+      "sheaftVersion": "0.1.1",
+      "chartVersion": "0.2.2",
+      "compatibilityState": "candidate",
+      "evidence": "Pinned to https://github.com/MB3R-Lab/Bering/releases/download/v0.1.0/release-manifest.json plus https://github.com/MB3R-Lab/Sheaft/releases/download/v0.1.1/release-manifest.json and https://github.com/MB3R-Lab/Sheaft/releases/download/v0.1.1/compatibility-manifest.json; verified by local generic smoke, local generic e2e, live kind-based generic smoke with locally rebuilt images, live kind-based generic smoke with anonymous pulls of the pinned GHCR images, repository CI pinned-image smoke on every push, OTel Demo profile smoke/e2e, and adapter end-to-end contract runs on 2026-03-16.",
+      "contracts": {
+        "collectorExport": "v1alpha1",
+        "discoveryReport": "v1alpha1",
+        "gateDecision": "v1alpha1",
+        "reportPayload": "v1alpha1"
+      },
+      "dashboards": {
+        "bering": "1.0.0",
+        "sheaft": "1.0.0"
+      },
+      "notes": [
+        "Bering v0.1.0 release contracts and Sheaft v0.1.1 compatibility pins align on io.mb3r.bering.model@1.0.0 and io.mb3r.bering.snapshot@1.0.0 digests.",
+        "This remains a candidate integration statement rather than a GA support claim.",
+        "Pinned GHCR image pullability is now demonstrated without credentials, but Sheaft serve/watch remains preview-grade upstream behavior and is not upgraded to a long-term stable contract by this bundle release."
+      ]
+    },
     {
       "stackVersion": "0.2.1",
       "beringVersion": "0.1.0",

compat/stack-manifest.json

@@ -3,27 +3,27 @@
   "schemaVersion": "1.0.0",
   "stack": {
     "name": "mb3r-stack",
-    "version": "0.2.1",
+    "version": "0.2.2",
     "status": "candidate",
-    "releaseDate": "2026-03-15",
+    "releaseDate": "2026-03-16",
     "notes": [
       "Generic integration and distribution layer only. No upstream Bering or Sheaft source code is vendored here.",
       "Candidate bundle pinned to released Bering v0.1.0 and Sheaft v0.1.1 artifacts with immutable GHCR digests.",
       "OpenTelemetry Demo is packaged as an example profile, not as the core contract.",
-      "This patch release adds a second live Kubernetes smoke for the generic synthetic profile that exercises the chart's pinned GHCR images without local image repackaging.",
-      "Cross-repository GHCR pullability remains an external operational precondition that must be validated with explicit credentials or public package access."
+      "This patch release captures the always-on pinned-image generic smoke path after upstream Bering and Sheaft GHCR packages were opened for anonymous pull.",
+      "Pinned GHCR images are now verified both locally and in repository CI without credential overrides."
     ]
   },
   "artifacts": {
     "chart": {
       "name": "mb3r-stack",
-      "version": "0.2.1",
+      "version": "0.2.2",
       "ociRepository": "oci://ghcr.io/mb3r-lab/charts",
-      "package": "mb3r-stack-0.2.1.tgz"
+      "package": "mb3r-stack-0.2.2.tgz"
     },
     "assetPack": {
-      "version": "0.2.1",
-      "archive": "mb3r-assets-0.2.1.tgz",
+      "version": "0.2.2",
+      "archive": "mb3r-assets-0.2.2.tgz",
       "includes": [
         "collector/",
         "dashboards/",
@@ -35,8 +35,8 @@
       "sheaft": "1.0.0"
     },
     "configPacks": {
-      "collector": "0.2.1",
-      "examples": "0.2.1"
+      "collector": "0.2.2",
+      "examples": "0.2.2"
     }
   },
   "components": {

docs/compatibility.md

@@ -24,11 +24,11 @@ The machine-readable compatibility contract is split across:
 
 ## Current Bundle
 
-`mb3r-stack` `0.2.1` currently tracks:
+`mb3r-stack` `0.2.2` currently tracks:
 
 - Bering `0.1.0`
 - Sheaft `0.1.1`
 
-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. A pinned-image live smoke now exists for clean-cluster startup checks, but proving cross-repo GHCR pullability still depends on explicit external credentials or public package access.
+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 pinned-image live smoke now passes against anonymous public GHCR pulls, but that does not change the formal maturity of the bundle or the upstream preview status of Sheaft serve/watch behavior.
 
 OpenTelemetry Demo can be used as one profile and one acceptance scenario, but it does not widen the formal compatibility statement on its own.

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.2.1
+  - component: $CI_SERVER_FQDN/group/mb3r-stack/bering-discover@v0.2.2
 ```
 
 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.2.1') _
+@Library('mb3r-stack@v0.2.2') _
 ```

examples/github/example-caller.yml

@@ -5,7 +5,7 @@ on:
 
 jobs:
   bering:
-    uses: ORG/mb3r-stack/.github/workflows/bering-discover.yml@v0.2.1
+    uses: ORG/mb3r-stack/.github/workflows/bering-discover.yml@v0.2.2
     with:
       command: |
         python - <<'PY'
@@ -20,7 +20,7 @@ jobs:
 
   sheaft:
     needs: bering
-    uses: ORG/mb3r-stack/.github/workflows/sheaft-gate.yml@v0.2.1
+    uses: ORG/mb3r-stack/.github/workflows/sheaft-gate.yml@v0.2.2
     with:
       discovery-artifact-name: ${{ needs.bering.outputs.artifact-name }}
       command: |
@@ -38,7 +38,7 @@ jobs:
     needs:
       - bering
       - sheaft
-    uses: ORG/mb3r-stack/.github/workflows/mb3r-report.yml@v0.2.1
+    uses: ORG/mb3r-stack/.github/workflows/mb3r-report.yml@v0.2.2
     with:
       discovery-artifact-name: ${{ needs.bering.outputs.artifact-name }}
       gate-artifact-name: ${{ needs.sheaft.outputs.artifact-name }}

examples/gitlab/.gitlab-ci.yml

@@ -4,7 +4,7 @@ stages:
   - report
 
 include:
-  - component: $CI_SERVER_FQDN/group/mb3r-stack/bering-discover@v0.2.1
+  - component: $CI_SERVER_FQDN/group/mb3r-stack/bering-discover@v0.2.2
     inputs:
       stage: discover
       command: |
@@ -17,7 +17,7 @@ include:
             encoding="utf-8",
         )
         PY
-  - component: $CI_SERVER_FQDN/group/mb3r-stack/sheaft-gate@v0.2.1
+  - component: $CI_SERVER_FQDN/group/mb3r-stack/sheaft-gate@v0.2.2
     inputs:
       stage: gate
       command: |
@@ -30,6 +30,6 @@ include:
             encoding="utf-8",
         )
         PY
-  - component: $CI_SERVER_FQDN/group/mb3r-stack/mb3r-report@v0.2.1
+  - component: $CI_SERVER_FQDN/group/mb3r-stack/mb3r-report@v0.2.2
     inputs:
       stage: report