Added
- The CLI runner is on nuget.org.
dotnet tool install --global Routebase.Cliinstallsroutebase— run test suites with JUnit output your CI renders as a real test report, run security scans with SARIF export and a threshold gate, promote a version after a deploy, and pull documentation as Markdown files out of the Doc Hub and write it back, with optimistic concurrency,--dry-run, and the guarantee that it never deletes anything. From 1.0.0 on, exit codes and flag names are part of the contract. US-hosted organizations set their region once withroutebase config set-region us, or per pipeline withROUTEBASE_REGION. A new CLI section in the docs covers all of it. See the CLI overview. - SSO setup guides for Okta, Microsoft Entra ID, Google Workspace, OneLogin and Ping Identity. Each one walks the order that actually works: create the SAML application at your identity provider with placeholders, create the connection in Routebase, then carry the real Entity ID and ACS URL back. They name the exact pages — Domains, Single Sign-On, API Keys and Audit Log each have their own — and the one step people miss: a domain verified after the connection exists needs the connection saved once more before it routes. New portal section SSO Setup, linked per provider from the SSO page.
- A folder in the Doc Hub is a working surface. Clicking a folder or a section opens an overview beside the tree: its slug, a description field that saves when you leave it, the numbers that matter (pages, changes since the last publish, last edit and who made it), and its contents as a list you can reorder by handle — the same call as dragging in the tree, so both show the same order. Every page edited since the last successful portal build carries a "Changed since publish" dot, subfolders roll their pages up, and the header names the total. Create a page or subfolder, rename, change a slug or delete right from the surface. Read-only versions show the same overview without the fields and handles.
- The documentation opens on a version overview. Instead of an empty pane, the Doc Hub greets you with the state of the version you are in: whether it is live and at which address, how the last portal build went, and whether an embedded API specification has moved on since.
- PHP code samples — and a language selection that takes effect. PHP joins the generated samples, built on the cURL extension every PHP installation ships with, version header included. And the languages you pick in the documentation settings are exactly the tabs that appear, in the app and on the published portal alike. Deliberately forgiving: no selection, or one that matches nothing, still shows every language — an endpoint page without a code sample would be the worse outcome. Existing portals pick this up on their next build, which re-uploads every page.
- A test suite sets its fixture scope. All fixtures (the default), only the selected ones, or all except the selected ones, across the project's fixtures and those imported from the organization library — the latter under the name a run actually resolves them by, alias included.
update_test_suitetakes the scope over MCP too. The scope is per suite, not per test case, and that is deliberate: a suite loads its fixtures once for every case, so values captured withCaptureToFixtureNamestay visible to later ones. - The branch workflow has the surfaces it was missing. The Merge Requests page opens on four figures — open requests, merges in the last 30 days, the share of merges carrying breaking changes, and the average time from opening to merge — and splits into Requests and History, the merges in the order they actually landed, each with the changes recorded at its merge. A merge request's detail view carries a History tab with its review trail. Manage Branches in the branch picker opens the full branch list for the current version, closed and merged ones included, filterable by status — and the one place to close a branch. Merges from before this release carry no timestamp and are left out of all four figures rather than counted as zero; the page says so.
Improved
- Reviewers are picked from your organization. Adding reviewers to a merge request is a searchable member list with avatars and roles, not a field asking for identifiers.
- A merge request states whether the branch breaks the contract — read from the actual diff between branch and base — and the merge policy can require an administrator's approval before such a branch lands.
- A test step blocked by a read-only environment reads the same everywhere. Routebase refuses write requests against an environment marked read-only before they reach the network and reports the case as Blocked, not failed. Scenario runs now say so as plainly as suite runs do, and the summary toast at the end of a run counts Blocked and Pending as their own states rather than folding them into failures.
Changed
- Billing access rests on two permissions.
billing:read— every member — carries the plan and limit information the product uses to explain why something is gated.billing:manageis owner-only and governs the billing pages and every change to a subscription.