Skip to content

ci: delete the crates.io publish job - #45

Merged
mlevkov merged 1 commit into
mainfrom
ci/drop-the-crates-io-publish-job
Sep 24, 2026
Merged

mlevkov merged 1 commit into
mainfrom
ci/drop-the-crates-io-publish-job

Conversation

@mlevkov

@mlevkov mlevkov commented Sep 24, 2026 •

Copy link
Copy Markdown
Owner

Summary

Deletes release.yml's crates.io publish job: iggy_sample is not published to
crates.io, so this resolves TD-2026-09-04 with its first option. The job could
not succeed (no CRATES_IO_TOKEN, and publish = false) and failed on every
stable release, hidden by continue-on-error.

Type of Change

  • CI/CD changes
  • Documentation update

Changes Made

  • release.yml: the publish job is gone; no workflow references
    CRATES_IO_TOKEN. publish = false stays as the guard.
  • Verifier: for a release.yml without the job, "no publish job" PASSes
    against publish = false (was a SKIP), and "every job succeeded" drops its
    exception. Runs up to v0.4.1 are checked against their own release.yml, so
    they still FAIL on the masked step, as before.
  • Docs: TD-2026-09-04 resolved (record and index); the verifier and
    workflow headers, CONTRIBUTING, Cargo.toml's comment and the changelog
    (a Removed entry) updated; TD-2026-09-05's pin count is 16 now.

Testing

  • Manual testing performed
shellcheck -s bash scripts/*.sh
scripts/verify-release.sh v0.4.1          # unchanged: 40 passed, 1 failed, 0 skipped
# with the job detection forced off, the same run gives
# "PASS no publish job ..." and "PASS every job succeeded"
cargo metadata --locked --format-version 1 --no-deps

Checklist

Documentation

  • Code comments explain "why" not "what"

Security

  • No secrets or credentials committed
  • No new security vulnerabilities introduced (removes a secret reference)

The maintainer ruled out publishing iggy_sample to crates.io, which
resolves TD-2026-09-04 with its first option. The job could not succeed
(no CRATES_IO_TOKEN, and publish = false) and failed on every stable
release under continue-on-error, so it only added a masked failed step
and a secret reference that invited configuring a live token. publish =
false stays as the guard, and no workflow references the secret now.

Verify Release checks each run against the release.yml that run used, so
the stable releases up to v0.4.1 still fail it on that step. For a
release.yml without the job, the verifier now PASSes "no publish job"
against publish = false instead of skipping, and "every job succeeded"
drops its exception. The verifier's and the workflow's headers,
CONTRIBUTING, Cargo.toml's comment and the changelog say so, the record
is resolved, and TD-2026-09-05's pin count drops to 16 with the job's
rust-cache pin.

Checked: v0.4.1 unchanged (40/1/0); with the job detection forced off,
the same run gives "PASS no publish job ..." and "PASS every job
succeeded".
@mlevkov
mlevkov merged commit b0a126f into main Sep 24, 2026
30 checks passed
@mlevkov
mlevkov deleted the ci/drop-the-crates-io-publish-job branch September 24, 2026 22:58
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