Breaking changes from 0.12.11

These old capabilities have a direct or bounded modern path. Review every converted rule before enabling it.

• Block lists become modern Block rules when their filters are valid.
• Standalone HSTS rules become Upgrade to HTTPS rules; the browser’s native HSTS behavior remains separate.
• Custom URL redirects convert only when their match and substitution can be represented safely; changed encoding or scope requires review.
• Hotlink protection can be recreated as a narrowly scoped request-header rule with explicit asset hosts and initiator domains.
• Old category switches become per-rule enabled intent, but migrated candidates remain disabled until review and permission approval.

The rebuild deliberately does not restore broad, obsolete, or unrelated browser behavior.

• Request logging: use the browser Network panel or export a HAR during a focused debugging session. RequestOrbit does not retain browsing history.
• Global CORS override: configure the server, use a development reverse proxy, or run a dedicated local test environment. There is no safe global equivalent here.
• User-Agent override and presets: use browser developer tools for temporary testing or server-side feature flags.
• Programmable context-menu actions: use browser bookmarks for static destinations or a separately reviewed automation tool for scripted behavior.
• Google search redirect: configure the browser’s search engine, or create a narrow Redirect rule only when a fixed URL shape is sufficient.
• Google-to-useso CDN rewriting: remove the old rule and use a maintained CDN or self-hosted assets; the historical endpoint is obsolete.
• QR generation: use browser or operating-system sharing tools where available.
• Icon styles, donation UI, telemetry, and remote services have no replacement inside RequestOrbit.

The old engine could execute JavaScript-era placeholder logic for host, path, and query values. Manifest V3 redirects use a narrower regular-expression substitution model.

Order-independent query extraction, computed placeholders, unsupported regular-expression syntax, more than nine captures, and non-HTTP(S) destinations stay disabled and exportable. Recreate them only after simplifying the URL contract.

Treat migration as a review, not as a one-click activation.

• Export the migration report and raw snapshot before applying anything.
• Start with automatic Block and HTTPS-upgrade candidates.
• Test every Redirect with representative paths, query strings, resource types, and initiators.
• Replace broad hotlink or header behavior with explicit initiator domains.
• Keep removed and unsupported records only as long as you need the audit trail.
• Export a current-format backup after the final rule set is stable.