Skip to content

v0.123.1

Choose a tag to compare

@smm-h smm-h released this 19 Sep 14:52
· 1472 commits to main since this release

Three release-blocking defects fixed: a Go module rename now moves the committed strictcli schema dump, a stale dev-sync overlay entry explains itself, and a red CI verdict prints the failing job's log again.

Context

All three surfaced in one release of a Go project that had just been renamed onto
its organization's module path.

The rename swept go.mod tokens and import sites but left .strictcli/schema.json
claiming the old project_id, so the release's schema-dump step refused and there
was nothing to do but delete the dump by hand; the sweep now plans and rewrites
that line too.

The release's version-skew guard read a dev-sources.toml.local-only overlay whose
checkout was long gone -- a leftover from a dependency era that had ended -- and
refused with a bare "path does not exist". Blocking stays, by design; the message
now names the file, what it is for, and both ways out.

And the failure summary could not fetch any job log that carried terminal colour,
because gh refuses to emit escape sequences unless told to, so a red candidate
printed a run URL and no error lines.

Fixes

  • rewrite go-module-path moves the strictcli schema dump. A Go module rename left the committed .strictcli/schema.json on the old identity, so the next schema dump refused and the release's schema-dump step failed with no remedy. The sweep now plans and rewrites the dump's project_id alongside every go.mod token and import site.
  • A stale dev-sync overlay entry now explains itself. An [[overlay]] block in dev-sources.toml.local-only whose checkout path no longer exists blocked rlsbl release run with a bare "path does not exist". The refusal now names the file and what it is for, calls the entry stale, and gives both remedies: repoint path, or delete the block (and the file with it when it was the only one).
  • A red CI verdict prints the failing job's log again. Fetching a job log through gh api failed with a non-zero exit whenever the log carried terminal colour, so the failure summary showed a run URL and no error lines, and the failure classification that decides whether to retry never ran. The read now allows escape sequences.