Repository navigation
docs: lead security page with IP ranges and network access - #20
Merged
Merged
Conversation
|
Jakub Krehel (jakubkrehel)
approved these changes
Oct 12, 2026
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
2 participants
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.
The security page now opens with IP ranges and workspace network access. The IP section links the machine-readable IPv4/IPv6 feed and explains that it covers Interfere-owned address space, so customers do not mistake it for every service's egress. The existing Enterprise network restrictions section moves alongside it, with explicit whitelist wording and its setup, permission, and recovery guidance preserved.
Publishing dependency: deploy and verify
https://interfere.com/ips.jsonbefore merging this PR.Validation passed:
bun run format,bun run lint,bun run typecheck,bun run validate,bun run check:links, andgit diff --check. Verified feature copy against the product implementation. The local Mintlify preview started successfully; visual browser inspection was unavailable because no browser is connected in this environment.