docs: weekly update — 2026-08-01 - #124
Draft
dobby-coder[bot] wants to merge 2 commits into
Draft
Conversation
…encryption4all/postguard-js#151) The SDK never shipped a notify-shape validator; the pg-js test suite pins its removal. `{ notify: true }` sends no mail and suppresses the silent-upload notice instead of throwing.
postguard-website, postguard-tb-addon, postguard-outlook-addon and postguard-examples were folded into the postguard-js pnpm workspace and archived (encryption4all/postguard-js#132, #134, #137, #141, #145). Cryptify's source moved into the postguard Cargo workspace, with image publishing left behind in its own repository (encryption4all/postguard#277).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Weekly docs drift pass over what merged in encryption4all since 2026-07-25. Two things landed that the docs got wrong, both verified against the source rather than the PR descriptions.
postguard-js: the notify validator that was removed
docs/sdk/js-encryption.mdsaid the SDK validates thenotifyshape and throwsTypeErroron{ notify: true }. It does not. The onlyTypeErrors inpackages/pg-js/src/sealed.tsare the twoReadableStreamguards, and the test suite pins the validator's removal. The real behaviour is quieter and worse:delivery?.recipientson a boolean isundefined,notifyRecipientsfalls back tofalse, no mail is sent, and becauseopts?.notify !== undefinedthe one-time silent-upload notice is suppressed too. The page now says that and points at{ notify: { recipients: true } }.Source: encryption4all/postguard-js#151, which fixed the same claim in the examples' READMEs.
Repository consolidation
Four repositories were folded into the
postguard-jspnpm workspace and archived, and Cryptify's source moved into thepostguardCargo workspace. The repo pages still linked to the archived repositories as the place the code lives. Archived repos keep serving files with 200, so nothing was visibly broken, only wrong.postguard-js(single package)packages/pg-jspostguard-websiteapps/websitepostguard-tb-addonapps/tb-addonpostguard-outlook-addonapps/outlook-addonpostguard-examplesexamples/*, on the workspace SDKcryptify(own lockfile)cryptify/in the postguard workspaceChanged:
docs/repos/overview.md(tables, the dependency graph, and a note on why one lockfile matters for the container header), the header lines of the seven moved project pages pluscryptify.md, andCLAUDE.md's snippet source list.Cryptify is the one that is half-moved on purpose: the source is a workspace member, but the
cryptifyrepository still builds and pushesghcr.io/encryption4all/cryptifybecause renaming that package is an ops decision. The page says so rather than picking one.Existing pinned-commit source links into the archived repositories were left alone. They resolve, and rewriting 60+ of them belongs in its own PR if you want it.
Checked and skipped
/readyz, docs: weekly update — 2026-06-06 #114 connection pooling, chore: update dependencies #115 structured logging: real changes, butdocs/repos/postguard-business.mdhas no health-endpoint or env-var surface to go stale. Adding one is a new section, not drift.dobby-code.irma-documentationhas no status list surface to update.npm run docs:buildis green.