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
Breaking: a release now stops when any push run of the verify
workflow on the tagged commit failed, on any branch, even if another run
succeeded. A failed run that was re-run to a pass counts as passed.
Breaking: a commit that renames a file out of a code path is no
longer read as documentation only, so its parent's run no longer stands
in for its own.
Breaking: image-build.yml accepts an image only when the version it
prints is the tag exactly, followed by whitespace or nothing, so v1.2.30 or v1.2.3-dirty no longer passes for v1.2.3.
Breaking: the release tag is applied only to a reference written <registry>/<path>@sha256:<64 hex digits>, with no tag.
Breaking: a files or evidence line of publish-release is one
path or pattern, so a path may hold a space; a line that held several
patterns separated by spaces now names one that matches nothing. A file
name with # is refused, since gh reads it as a label.
Breaking: tools/repo-settings.sh fails when the repository listing
fails partway, when the policy file or a repository answer is not JSON,
and when a write is refused with anything but the validation error
(HTTP 422) GitHub gives for open classic projects, which alone is
retried without has_projects. A repository left with projects enabled
is still PARTIAL, counted apart in the summary, and leaves the exit
status 0.
A re-run of a publish over an existing release restates its title and
prerelease flag along with the notes.
Each attempt of an image deploy's smoke is stopped when smoke_timeout
is up, and a failed smoke's last OUTPUT_MD is appended to the step
summary.
An image namespace with -- or __, which a reference allows, is
accepted; one holding a newline is refused.
The starter callers name ci.yml as the workflow an image release
verifies, take the workflow_dispatch the pin move sends, pass smoke
evidence only when the deploy ran, and name an example service.
The runner policy in the README now reads hosted runners for every
repository: private repositories run only scheduled and hand-started jobs
there, and their push, release and deploy run from a workstation.
Breaking: image-build.yml takes an empty verify_workflow by
default, which reads as the one workflow in .github/workflows that
calls lateregate.yml, as the other pipelines do. It defaulted to verify.yml, so a caller that passed nothing and has no verify.yml was
refused; a repository with several callers must now name the workflow.
Breaking: service-release.yml and image-deploy.yml run the
rollback guard a second time right before the kubeconfig is written. An
older release that finishes late, after a newer vX.Y.Z was tagged, now
stops there instead of rolling production back; the build it paid for is
lost.
Pushing a v1.MINOR.PATCH tag moves v1 only after the tagged commit
passed this repository's own test.yml on its push, so a tag cut on a
red or unverified commit no longer reaches the callers that pin @v1.
Breaking: in cli-release.yml the verified job holds contents: read and actions: read, the test job contents: read, and only the goreleaser job contents: write. The consumer's tests no longer run
with a token that can write to the repository. A caller's .goreleaser.yaml hook that read workflow runs from the release job
needs its own grant.
Breaking: cli-release.yml publishes only when every leg of the test_os matrix succeeded. A canceled leg used to let the release
through; it now stops it.
Breaking: service-release.yml refuses build_cli: true with no cli_build_cmd in its first step. It used to fail only at the publish,
after the build and the deploy had gone out.
A release on a commit whose verify workflow has no push run now counts a
successful workflow_dispatch run of that workflow on the default branch
for the exact commit, as verified. This is the run ci-gate-bump.yml
dispatches for its pin commit, which a push with the job's token does not
start, so a release on a pin commit is no longer blocked. A failed push
run of the commit, on any branch, still blocks the release, and so does a
dispatched run on another branch or one that did not succeed.
Breaking: the test job of lateregate.yml is named test (<os>),
not test on <os>, so it shows no raw ${{ matrix.os }} when it is
skipped. A branch protection rule that requires a check by the old name
needs the new one.
Fixed
A smoke script that passes without writing OUTPUT_MD no longer fails
the deploy.
The digest check of an image deploy no longer reports that the overlay
names no image when the rendered overlay is large.
A wait_minutes such as 08 is read as eight minutes instead of failing.
A commented-out call to lateregate.yml no longer counts as a second
per-push workflow.
ensure-kustomize no longer takes an installed v5.8.30 for the pinned 5.8.3.
signed-checksums sums a file whose name starts with -.
tools/repo-settings.sh --help exits 0, and a repository it cannot read
is reported with gh's error instead of a list of drifted fields.
An image release passes evidence to publish-release only when a .md
file was downloaded, so an evidence pattern that matched no Markdown no
longer fails the publish.
A backport tag such as v1.5.1, pushed after v1.6.0, no longer moves v1 backwards: v1 moves only to the highest v1.MINOR.PATCH release
tag.