Prepare v0.3.1 patch release

Author: a-a-k

CHANGELOG.md

@@ -2,6 +2,15 @@
 
 ## Unreleased
 
+## v0.3.1
+
+### Fixed
+
+- Schema publishing is now a completed part of the shipped release path rather than a post-release manual recovery step.
+- The GitHub Pages schema publication workflow now resolves pinned schema constants and step outputs correctly for both tag-driven and manual runs.
+- README release badges now match the Sheaft header pattern and point at the current Bering release line.
+- Release-facing docs now consistently describe `v0.3.1` as the current product line carrying the published `1.1.0` schema contracts.
+
 ## v0.3.0
 
 ### Added

README.md

@@ -5,10 +5,10 @@
 [![ci](https://img.shields.io/github/actions/workflow/status/MB3R-Lab/Bering/ci.yml?branch=main&label=ci)](https://github.com/MB3R-Lab/Bering/actions/workflows/ci.yml)
 [![publish-schema](https://img.shields.io/github/actions/workflow/status/MB3R-Lab/Bering/publish-schema.yml?branch=main&label=publish-schema)](https://github.com/MB3R-Lab/Bering/actions/workflows/publish-schema.yml)
 [![Go version](https://img.shields.io/github/go-mod/go-version/MB3R-Lab/Bering)](https://github.com/MB3R-Lab/Bering/blob/main/go.mod)
-[![Status](https://img.shields.io/badge/status-current_release-blue)](https://github.com/MB3R-Lab/Bering/releases/tag/v0.3.0)
+[![Status](https://img.shields.io/badge/status-current_release-blue)](https://github.com/MB3R-Lab/Bering/releases/tag/v0.3.1)
 [![Public schema](https://img.shields.io/badge/public_schema-1.0%20%7C%201.1-blue)](https://github.com/MB3R-Lab/Bering/blob/main/VERSIONING.md)
 
-`Bering v0.3.0` is the current product release of Bering: a discovery and publishing layer for service topology and endpoint contracts.
+`Bering v0.3.1` is the current product release of Bering: a discovery and publishing layer for service topology and endpoint contracts.
 
 Bering turns trace input or explicit topology input into stable JSON artifacts, and it can also run as a long-lived runtime service that emits rolling discovery snapshots plus conservative reconciliation views for trace gaps.
 
@@ -28,8 +28,8 @@ Bering owns discovery and discovery-side public contracts. It does not own simul
 
 Do not treat the product release tag as the schema contract version.
 
-- Current product release for this repository: `Bering v0.3.0`
-- Current product git tag / GitHub Release: `v0.3.0`
+- Current product release for this repository: `Bering v0.3.1`
+- Current product git tag / GitHub Release: `v0.3.1`
 - Default emitted schema contracts now are:
   - `io.mb3r.bering.model@1.1.0`
   - `io.mb3r.bering.snapshot@1.1.0`
@@ -60,7 +60,7 @@ Also packaged today:
 Example:
 
 ```bash
-tar -xzf bering_0.3.0_linux_amd64.tar.gz
+tar -xzf bering_0.3.1_linux_amd64.tar.gz
 ./bering help
 ```
 

RELEASING.md

@@ -9,7 +9,7 @@ Product releases and schema publishing are separate operations:
 - product release tags: `vX.Y.Z`
 - schema publishing tags: `schema-vA.B.C`
 
-Product releases advance independently from the public schema contracts. As of the current release line, use `v0.3.0` for the product release while the default emitted public schema contracts are `1.1.0` and the preserved `1.0.0` contracts remain available for validation and pinned consumers.
+Product releases advance independently from the public schema contracts. As of the current release line, use `v0.3.1` for the product release while the default emitted public schema contracts are `1.1.0` and the preserved `1.0.0` contracts remain available for validation and pinned consumers.
 
 ## Prerequisites
 
@@ -28,7 +28,7 @@ Dry-run without publishing:
 
 ```bash
 make release-dry-run \
-  VERSION=0.3.0 \
+  VERSION=0.3.1 \
   GIT_SHA="$(git rev-parse HEAD)" \
   BUILD_DATE="$(git show -s --format=%cI HEAD)"
 ```
@@ -37,7 +37,7 @@ Full local release payload with OCI publish:
 
 ```bash
 make release-local \
-  VERSION=0.3.0 \
+  VERSION=0.3.1 \
   GIT_SHA="$(git rev-parse HEAD)" \
   BUILD_DATE="$(git show -s --format=%cI HEAD)" \
   IMAGE_REPOSITORY=ghcr.io/mb3r-lab/bering \
@@ -49,8 +49,8 @@ If the chart version must intentionally differ from the app version:
 
 ```bash
 make chart-package \
-  VERSION=0.3.0 \
-  CHART_VERSION=0.3.1 \
+  VERSION=0.3.1 \
+  CHART_VERSION=0.3.2 \
   ALLOW_CHART_VERSION_MISMATCH=1
 ```
 
@@ -80,7 +80,7 @@ These variables control the release payload:
 - `CHART_VERSION`: optional explicit chart version
 - `ALLOW_CHART_VERSION_MISMATCH=1`: required when `CHART_VERSION != VERSION`
 
-For `v0.3.0`, `VERSION=0.3.0` while the default emitted public schema contracts are `1.1.0`.
+For `v0.3.1`, `VERSION=0.3.1` while the default emitted public schema contracts are `1.1.0`.
 
 ## Expected Output
 

VERSIONING.md

@@ -4,8 +4,8 @@ Bering separates product release versioning from public schema contract versioni
 
 For the current published product release:
 
-- product release tag: `v0.3.0`
-- product version in release automation: `0.3.0`
+- product release tag: `v0.3.1`
+- product version in release automation: `0.3.1`
 - schema publishing tag: `schema-v1.1.0`
 - default emitted schema contracts:
   - `io.mb3r.bering.model@1.1.0`
@@ -26,8 +26,8 @@ App version changes govern the Bering CLI, the runtime service behavior, the ins
 
 Examples:
 
-- product release `v0.3.0` identifies the current Bering release line
-- `dist/release-manifest.json` records `"app_version": "0.3.0"`
+- product release `v0.3.1` identifies the current Bering release line
+- `dist/release-manifest.json` records `"app_version": "0.3.1"`
 
 ## Schema Contract Versions
 
@@ -45,8 +45,8 @@ Each schema contract has its own version, URI, and digest. Those values are inde
 
 Examples:
 
-- Bering `v0.3.0` now emits `io.mb3r.bering.model@1.1.0`
-- Bering `v0.3.0` now emits `io.mb3r.bering.snapshot@1.1.0`
+- Bering `v0.3.1` emits `io.mb3r.bering.model@1.1.0`
+- Bering `v0.3.1` emits `io.mb3r.bering.snapshot@1.1.0`
 - `bering validate` still accepts `1.0.0` artifacts without mutation or migration
 - `schema-v1.1.0` publishes the schema files to GitHub Pages; it is not a product release tag
 

docs/install.md

@@ -1,6 +1,6 @@
 # Install
 
-Bering `v0.3.0` is the current product release. It emits `io.mb3r.bering.model@1.1.0` and `io.mb3r.bering.snapshot@1.1.0` by default, while still validating the preserved `1.0.0` contracts.
+Bering `v0.3.1` is the current product release. It emits `io.mb3r.bering.model@1.1.0` and `io.mb3r.bering.snapshot@1.1.0` by default, while still validating the preserved `1.0.0` contracts.
 
 ## Binary Archives
 
@@ -14,18 +14,18 @@ Supported release targets:
 - `darwin/arm64`
 - `windows/amd64`
 
-Example release asset names for `v0.3.0`:
+Example release asset names for `v0.3.1`:
 
-- `bering_0.3.0_linux_amd64.tar.gz`
-- `bering_0.3.0_linux_arm64.tar.gz`
-- `bering_0.3.0_darwin_amd64.tar.gz`
-- `bering_0.3.0_darwin_arm64.tar.gz`
-- `bering_0.3.0_windows_amd64.zip`
+- `bering_0.3.1_linux_amd64.tar.gz`
+- `bering_0.3.1_linux_arm64.tar.gz`
+- `bering_0.3.1_darwin_amd64.tar.gz`
+- `bering_0.3.1_darwin_arm64.tar.gz`
+- `bering_0.3.1_windows_amd64.zip`
 
 Example:
 
 ```bash
-tar -xzf bering_0.3.0_linux_amd64.tar.gz
+tar -xzf bering_0.3.1_linux_amd64.tar.gz
 ./bering help
 ```
 
@@ -40,8 +40,8 @@ go build ./cmd/bering
 Pull the published runtime image:
 
 ```bash
-docker pull ghcr.io/mb3r-lab/bering:v0.3.0
-docker run --rm ghcr.io/mb3r-lab/bering:v0.3.0 help
+docker pull ghcr.io/mb3r-lab/bering:v0.3.1
+docker run --rm ghcr.io/mb3r-lab/bering:v0.3.1 help
 ```
 
 The release manifest records all published image references and the final digest in `oci_images`.
@@ -51,13 +51,13 @@ The release manifest records all published image references and the final digest
 Install directly from the published OCI chart:
 
 ```bash
-helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.3.0
+helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.3.1
 ```
 
 Override the image repository, tag, or digest if you mirror artifacts:
 
 ```bash
-helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.3.0 \
+helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.3.1 \
   --set image.repository=ghcr.io/mb3r-lab/bering \
   --set image.digest=sha256:...
 ```
@@ -67,7 +67,7 @@ helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.3.0 \
 Download `bering-contracts_<version>.tar.gz` to consume the public schema contracts offline:
 
 ```bash
-tar -xzf bering-contracts_0.3.0.tar.gz
+tar -xzf bering-contracts_0.3.1.tar.gz
 cat contracts-manifest.json
 ```
 

docs/planning/minor-schema-contract-evolution/implementation-note.md

@@ -28,9 +28,9 @@
 ## Release And Publication Boundary
 
 - Product release versioning remains separate from schema contract versioning.
-- The current product line is `v0.3.0`, and it now emits `1.1.0` contracts by default.
+- The current product line is `v0.3.1`, and it emits `1.1.0` contracts by default.
 - The schema publication tag used for external publication is `schema-v1.1.0`.
-- The `1.1.0` schema line is now published on GitHub Pages and shipped by the `v0.3.0` product release.
+- The `1.1.0` schema line is now published on GitHub Pages and shipped by the `v0.3.1` product release.
 
 ## Explicit Non-Goals For This Minor
 

docs/schema-publishing.md

@@ -11,7 +11,7 @@ This workflow is separate from the product release workflow:
 
 For the current release line, that means:
 
-- product release: `v0.3.0`
+- product release: `v0.3.1`
 - schema publishing: `schema-v1.1.0`
 
 ## One-time repository setup