Skip to content

docs: README banner — development moved to postguard, crate is cryptify/ #204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rubenhensen merged 1 commit into from
Aug 7, 2026
Merged

docs: README banner — development moved to postguard, crate is cryptify/ #204

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,11 @@

> For full documentation, visit [docs.postguard.eu](https://docs.postguard.eu/repos/cryptify).

> [!IMPORTANT]
> **Development moved to [encryption4all/postguard](https://github.com/encryption4all/postguard), under `cryptify/`.**
> That repository builds the crate as a workspace member sharing a single lockfile with `pg-core`/`pg-pkg`. Open issues have moved there too.
> This repository is kept for history and will be archived once its Docker publish pipeline cuts over to `postguard`. Until then, this repository's CI is still the only publisher of `ghcr.io/encryption4all/cryptify` — do not remove its build/push steps yet.

@dobby-coder dobby-coder Bot Aug 8, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line is stale on main now, and it is the one place a reader would look before touching the publish pipeline.

It says the Docker cutover has not happened yet, and it tells the reader not to remove the build/push steps. #206 overtook both (merged 2026-08-07 14:00, 75 minutes after this PR): it removed those steps from .github/workflows/ci.yml (6 insertions, 104 deletions) and left README.md untouched. postguard#293, the cutover task this line points at, is CLOSED.

ci.yml's header comment now reads:

Docker publishing moved to encryption4all/postguard, which builds this crate as a workspace member and pushes the same ghcr.io/encryption4all/cryptify image name (postguard#293). This workflow no longer builds or pushes any image.

So the README and the workflow it describes contradict each other. The direction of the error is what makes it worth a follow-up: a reader trusting the README will preserve build/push steps that are already gone, or hold off archiving to wait for a cutover that already landed.

Suggested replacement for a follow-up PR (GitHub will not apply a suggestion block on a merged PR, so this is plain text):

> This repository is kept for history. Docker publishing has moved to `postguard`, which now pushes `ghcr.io/encryption4all/cryptify` (postguard#293). This repository's CI only runs the Rust quality gate and release-plz. Archiving is tracked in postguard#294.

That also drops the em dash, per the org README style rules.


File encryption and sharing service based on identity attributes. Cryptify is the file storage and delivery backend used by the PostGuard website and JavaScript SDK. When users upload encrypted files through PostGuard, they are stored and served by Cryptify.

Cryptify is a Rust service built on the Rocket framework.
Expand Down