0091. Release names are placeholders until Mik chooses them, and the pipeline is a dry run
- Status: Accepted (Mik, 17 Nov 2026). Decision 0161 chose the names and its rename filled them in, so the placeholders and the codename rewriting are gone; the pipeline is still a dry run
- Date: 2026-11-14
- Decided by: integrator (internal only), pending Mik's approval
- Planning item: D1, D2 (the public name); WP16 (release pipeline)
Context
The workspace packages are named @strata/*, the extension strata.strata-vscode, the crates strata-*. Decision 0010 makes "strata" a codename that must never reach a registry. @strata on npm also belongs to someone else. WP16 needs a release pipeline that can be exercised end to end now, before the public name exists, without any risk of publishing.
Decision
- Every public name is a placeholder until Mik fills it in in
tools/release/release.yaml: The CLI archives are namedcli-<version>-<target>, and the binary inside is named after the product, never the codename.- the npm scope (
scope: null; packs use@owner-scope), - the VS Code publisher (
publisher: null; packs useowner-publisher), - the extension's name (
name: null; packs useowner-language-support), - the product name (
product: null, so packs useowner-product) and its display form (display-name: null, so packs useOwner Product), - the docs domain (
strata explainprintshttps://docs.example.invalid, a reserved name that can never resolve).
- the npm scope (
- Staging rewrites everything that would carry the codename to a registry (
tools/release/codename.ts). In every string of every staged manifest, keys included, it rewrites the extension's id and name (soeditor.defaultFormatternames the new id), published package names,bincommands, the display name, and the CLI command in prose and in settings defaults. In staged JavaScript it rewrites the import and require specifiers of published packages. A few uses are kept, each with its reason, because they are not registry identities and the code that reads them changes with the rename: file names inside a package, the language id and page-file extension, the extension's setting and command ids, and the repository's address. Type declaration files and READMEs keep the module names pages import from (@strata/client), which the compiler resolves. With--strict, the dry run fails on any codename left in a manifest string beyond those kept uses, and on any import of a codename package that is not published. CI runs the dry run with--strict, and so does the release workflow. - The pipeline is a dry run.
.github/workflows/release.ymlruns only by manual dispatch, with adry-runinput that defaults to true. Its token can only read contents, no checkout keeps its credentials, and every action is pinned to a commit. It versions the release in its own checkout and builds the CLI on Linux, macOS and Windows. It packs the npm packages and the.vsix, checks each pack withnpm publish --dry-run, and uploads everything as build artifacts. There is no publish step. With dry run off, the first step of the first job stops the run with an error that names this decision, before anything is built.pnpm release:drydoes the same locally and prints what would be published.pnpm releasewithout--dry-runrefuses. - What a release will publish is listed in
release.yaml:client,kit,language-server,ts-plugin,effects,adaptersandmodules(added by WP13, which filled it) on npm, and the extension on the VS Code Marketplace and Open VSX. The empty placeholder packages wait for their work packages. crates.io, JetBrains Marketplace and docs hosting are listed as later.
Needs Mik
- The public name, and from it the product name and its display form, the npm scope, the VS Code publisher and extension name, and the docs domain. The integrator checks availability on npm, crates.io, both VS Code registries, JetBrains Marketplace and a domain (decision 0010).
- The registry accounts and their tokens (npm, VS Code Marketplace, Open VSX), stored as repository secrets.
- Permission to add the publish job. That job is the only place publishing will ever happen, after the rename.
Alternatives considered
| Option | Why not |
|---|---|
Pack under @strata/* and rename at publish time | A forgotten rename would publish the codename to a scope that is not ours. |
| Invent a plausible scope now | It might be taken, or chosen by accident. A placeholder that is obviously a placeholder cannot be mistaken for a decision. |
| Leave the publish job in, turned off by the input | One wrong click would publish. With no job, publishing needs a reviewed change. |
Consequences
- The dry run lists every codename use that staging keeps. The rename (decision 0010's superseding record) must change those uses together with the code that reads them: the language id and file extension, the setting ids and the module names pages import from.
- After the names are chosen,
release.yamlis the only file that changes for names. The publish job is a separate, reviewed change.
What Mik decided (17 Nov 2026)
Keep the placeholders for now. Releases stay a dry run, and nothing is published until Mik chooses the public name and adds the registry accounts; the list under "Needs Mik" still stands.