Repository navigation
Say exports are readable data, link what the host can see, require Node 24 - #18
Merged
Merged
Conversation
…de 24 The console and facilitator guide now say the exports are not sealed and should be stored like the key file. Self-hosting lists what Cloudflare can see and links the shared data-visibility page. package.json engines now match .node-version and the environment check (Node 24).
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.
docs/DATA-VISIBILITY.md. Those links resolve once the shared PR merges.enginesnow requires Node 24, matching.node-version, CI and the environment check.Checks: lint, unit tests (22), typecheck and UI check pass locally. Build and browser smoke tests are left to CI.