Repository navigation
fix: harden workspace notifications and production recovery (0.6.7) - #7
Merged
Merged
Conversation
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.
Workspace0.6.7 rechecks current notification authorization at dispatch, routing and immediately before SMTP, including destination selectors, revocation, archived workspaces and changed addresses. Static configured external broadcast recipients retain their semantics. Split uploads/presence preserve the client header only through the authenticated exact-origin gateway.
The standalone PostgreSQL/Redis/private Silo setup keeps BullMQ worker/beat delivery. Full backups quiesce active writers and avoid a reproduced GNU tar race; restore replaces the public schema transactionally and reinstates restricted runtime grants. Images safely own private700/600 public/operator inputs, stage PostgreSQL bootstrap files under its UID, remove npm/npx and retain Sharp/isolated Prisma tools. Independent cron dependencies are audited and bundled without credentials.
Completed final acceptance:
The coordinator's earlier source snapshot omitted a tracked nested backup route; the helper was corrected,2528/2528 tracked paths verified, and the full Linux/unit and native install/restore runs repeated from the complete source. Earlier partial assemblies are labelled historical. Final225a677 changes only the report; its CI is the merge gate.
See docs/PRODUCTION_AUDIT_2026-10-29.md and docker/caddy/README.md for exact identities, shared-vendor findings and limits. Review/drain pre-fix generic notification emails without source IDs before rollout. The user accepted local clean-stack tests and deferred actual VM/firewall/public DNS/TLS, real-provider and offsite restore checks. Merge through checked dev and main PRs; no live production data was used.