Skip to content
This repository was archived by the owner on Aug 9, 2026. It is now read-only.

chore: retire release-plz and finalize the archive banner - #207

Merged
rubenhensen merged 1 commit into
mainfrom
chore/retire-release-plz-before-archive
Aug 9, 2026
Merged

chore: retire release-plz and finalize the archive banner#207
rubenhensen merged 1 commit into
mainfrom
chore/retire-release-plz-before-archive

Conversation

@rubenhensen

Copy link
Copy Markdown
Contributor

Last change before encryption4all/cryptify is archived — the step 7 of postguard#294 that postguard#293 unblocked.

Retires release-plz-release / release-plz-pr. postguard#293 moved the Docker publish over but deliberately left these two jobs alone. They are not inert: PR #161 was closed as superseded on 2026-08-07 12:46 and release-plz-pr re-opened the identical PR (#205) at 12:47. The crate is versioned by postguard's workspace release-plz now — tags cryptify-v0.1.28 onward — so a second release-plz cutting bare v0.1.28 here is a duplicate of a release that already shipped. Removing them also means the merge of this PR can't re-open #205 a third time, and an archived repo can't close an open PR (read-only), so the ordering matters.

Rewrites the README banner, which still claimed this repository is the only publisher of ghcr.io/encryption4all/cryptify and that its build/push steps must not be removed. Both went false when postguard#293 landed, and once archived the README can't be corrected.

The quality job is left in place; archiving stops it from running anyway.

cryptify is versioned by postguard's workspace release-plz (tags
`cryptify-v*`) and its image is published by postguard's delivery.yml
since postguard#293. The release-plz jobs here were the last live half of
that cutover: they re-opened a duplicate `chore: release v0.1.28` PR one
minute after the previous one was closed, and archiving the repo with an
open PR would strand it read-only.

Also rewrites the README banner, which still told readers this repo was
the only publisher of ghcr.io/encryption4all/cryptify and that its
build/push steps must not be removed. Both are now false.
@dobby-coder

dobby-coder Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Thanks for the detailed writeup, @rubenhensen — I'm on it. Reviewing this PR now: removal of the release-plz-release/release-plz-pr jobs, the README banner rewrite, and the ordering rationale ahead of the archive.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant