Repository navigation
Release 1.16.0: private edit review, layout inbox and default history - #4
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
HTML Drop's edit mode already served sibling files but exposed the whole artifact folder, supported only loopback browsing, and retained layout warnings as a replaceable snapshot. This release constrains assets to safe declared dependencies, reloads linked files, adds expiring private reviewer gateways, and tracks visible layout findings through verified resolution at the exact viewport and render revision.
Every publish now includes document history independently of
--feedback. Readers can view prior versions and compare added/removed text; private revisions retain their original encryption, andpullpreserves history for the next publisher. Failed deploys restore local staging. A Worker fix also prevents a former public snapshot from remaining accessible after password protection is enabled.Excalidraw, shape comments and MCP remain planned together for milestone 2.
Validation:
npm test: 39 tests, plus 3 crypto and 10 access-token checks passed; includes real Chromium desktop/mobile interactions, reviewer authentication/comment/poll/reply/reload, deterministic live reply refresh, draft preservation during incoming updates and pending saves, stale CSS and concurrent audit regressions, private history/XSS, cross-machine pull, and failed-deploy rollback.tsc --noEmitandwrangler deploy --dry-runpassed; npm package contents checked.Operational note: enabling private feedback access precedes Surge deployment. If deployment subsequently fails, access remains protected and its prior capability may stop working until the same push is retried. The CLI reports this partial transition; it does not automatically reopen private access.