You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Patch release focused on post-audit hardening for the `v0.3.x` discovery/runtime
30
30
- Schema publishing is now a completed part of the shipped release path rather than a post-release manual recovery step.
31
31
- The GitHub Pages schema publication workflow now resolves pinned schema constants and step outputs correctly for both tag-driven and manual runs.
32
32
- README release badges now match the Sheaft header pattern and point at the current Bering release line.
33
-
- Release-facing docs now consistently describe `v0.3.1`as the current product line carrying the published `1.1.0` schema contracts.
33
+
- Release-facing docs now consistently describe the `v0.3.1` product line that carried the published `1.1.0` schema contracts at that point in the release history.
Copy file name to clipboardExpand all lines: RELEASING.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Product releases and schema publishing are separate operations:
9
9
- product release tags: `vX.Y.Z`
10
10
- schema publishing tags: `schema-vA.B.C`
11
11
12
-
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.
12
+
Product releases advance independently from the public schema contracts. As of the current release line, use `v0.3.3` 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.
13
13
14
14
## Prerequisites
15
15
@@ -28,7 +28,7 @@ Dry-run without publishing:
28
28
29
29
```bash
30
30
make release-dry-run \
31
-
VERSION=0.3.1 \
31
+
VERSION=0.3.3 \
32
32
GIT_SHA="$(git rev-parse HEAD)" \
33
33
BUILD_DATE="$(git show -s --format=%cI HEAD)"
34
34
```
@@ -37,7 +37,7 @@ Full local release payload with OCI publish:
37
37
38
38
```bash
39
39
make release-local \
40
-
VERSION=0.3.1 \
40
+
VERSION=0.3.3 \
41
41
GIT_SHA="$(git rev-parse HEAD)" \
42
42
BUILD_DATE="$(git show -s --format=%cI HEAD)" \
43
43
IMAGE_REPOSITORY=ghcr.io/mb3r-lab/bering \
@@ -49,8 +49,8 @@ If the chart version must intentionally differ from the app version:
49
49
50
50
```bash
51
51
make chart-package \
52
-
VERSION=0.3.1 \
53
-
CHART_VERSION=0.3.2 \
52
+
VERSION=0.3.3 \
53
+
CHART_VERSION=0.3.3-chart.1 \
54
54
ALLOW_CHART_VERSION_MISMATCH=1
55
55
```
56
56
@@ -80,7 +80,7 @@ These variables control the release payload:
80
80
-`CHART_VERSION`: optional explicit chart version
81
81
-`ALLOW_CHART_VERSION_MISMATCH=1`: required when `CHART_VERSION != VERSION`
82
82
83
-
For `v0.3.1`, `VERSION=0.3.1` while the default emitted public schema contracts are `1.1.0`.
83
+
For `v0.3.3`, `VERSION=0.3.3` while the default emitted public schema contracts are `1.1.0`.
0 commit comments