Skip to content

docs(fork): digest rows for the stable releases since 1.4.0, current carried-patch commits - #218

Merged
QuentinBisson merged 3 commits into
giantswarmfrom
docs/fork-release-rows-20261009
Oct 9, 2026
Merged

QuentinBisson merged 3 commits into
giantswarmfrom
docs/fork-release-rows-20261009

Conversation

@QuentinBisson

@QuentinBisson QuentinBisson commented Oct 9, 2026 •

Copy link
Copy Markdown

Problem

The Digests table stops at 1.4.0 (and 1.1.3, 1.3.2) while 1.1.4, 1.2.0, 1.3.0, 1.3.3 to 1.3.7, 1.5.0 and 1.6.0 exist, and v0.0.27-gs.9 sits at the end. The carried-patch table cites commits from before the re-pins, still describes the dropped golden boot bound, says the default egress policy line carries the now-closed agent-substrate#1558, and dates the status migration to an unpromoted 1.4.1.

Change

Adds the missing rows with their gsoci digests (1.1.4 was tagged but never published), moves gs.9 into order, and points every Fork commit at the commit on giantswarm (git log v0.4.0-alpha1..giantswarm). The golden boot row now describes only the carried output tail; the egress row exits on agent-substrate#2159; the status migration row names 1.5.0 as its first stable release.

…nt carried-patch commits

Rows for 1.1.4 (never published), 1.2.0, 1.3.0, 1.3.3 to 1.3.7, 1.5.0 and 1.6.0, with the
gsoci digests of their images and charts; v0.0.27-gs.9 moves to its place. The carried-patch
table cites the commits on giantswarm instead of the pre-re-pin ones.
@QuentinBisson
QuentinBisson marked this pull request as ready for review October 9, 2026 06:43
@QuentinBisson
QuentinBisson requested a review from a team as a code owner October 9, 2026 06:43
@QuentinBisson
QuentinBisson merged commit 14d5770 into giantswarm Oct 9, 2026
17 checks passed
@QuentinBisson
QuentinBisson deleted the docs/fork-release-rows-20261009 branch October 9, 2026 07:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant