npm / @scalar/workspace-store
@scalar/workspace-store
What changed in @scalar/workspace-store 0.68 to 0.69, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-24.
2 breaking3 behavior and defaults20 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@scalar/workspace-store 0.691 changes
Behavior and default changes 1
Undici 8 enables HTTP/2 by default.
@scalar/workspace-store 0.6824 changes
Breaking changes 2
Private-network document requests are blocked by default; local files require an explicit basePath. External references follow the same permissions, with an opt-in for trusted private-network inputs.
Badges and audience labels no longer appear in navigation groups; they display on operations instead.
Behavior and default changes 2
Operation metadata and replies inherit from traits using recursive merge rules, and inherited titles appear in navigation.
Optional enum parameters stay disabled until explicitly enabled when they have no default or example, and declared schema examples take precedence over enum suggestions.
Fixes and other changes 20
Serialized JSON examples are generated from contentSchema instead of falling back to null, including JSON media type parameters, structured JSON suffixes, and string type arrays.
Render external documentation for servers, channels, operations, messages, tags, and schemas, including referenced objects and descriptions, using the existing OpenAPI link presentation.
Keep messages searchable when navigation renders them beneath operations.
Ignore sibling properties when rendering content, navigation, search, and schemas.
Preserve API key name edits for export, allow configured names to be cleared, and release configured overrides when the default name is restored.
The untagged webhooks sidebar section now uses this id instead of
{document}/webhook/undefined/.Preserve recursive schemas in generated request bodies, code samples, and response examples instead of replacing recursion points with null or empty arrays.
Boolean schemas with explanations are rendered in message payloads, headers, and reusable models.
Every visible channel message is documented while operation-specific message subsets, links, and server/protocol filtering are preserved.
Channel messages appear only when they are not used by an operation, and the sidebar stays in sync.
Escaped channel and message identifiers resolve correctly in AsyncAPI navigation.
Inline security schemes and scopes are rendered, while server authentication remains separate from operation security.
Reset to default appears only when a field has a different default; cleared OAuth2 access tokens retain the action. Show password appears only when a field has a value, and emptied fields return to masked.
Cookie paths follow the RFC 6265 path-match algorithm, so a cookie restricted to
/apiis not sent with requests to/apiv2.Expanded query parameter checkboxes operate independently; disabled field values are preserved but excluded from requests.
Channels and their messages render even when no operations reference them, with server and protocol filtering.
OpenAPI 3.2 allowReserved is honored for path parameters while forbidden path characters are escaped and the encoded path is preserved in Ruby code examples.
Form body fields resolve structural allOf object fields, annotation-only wrappers, and selected oneOf/anyOf variants, preserving descriptions, nested inputs, and multipart value types when switching variants.
OpenAPI 3.2 security requirements resolve by URI, including relative references based on the document URI, while named schemes and authored exports are preserved.
Invalid non-exploded structured cookies are reported, and invalid request and code sample generation is prevented. The notes recommend style: cookie with explode: true.