Rslint extension sunset checklist #86

Retire the standalone Rslint extension (rstack.rslint, web-infra-dev/rslint packages/vscode-extension) in favor of rstack.rstack, following the same process as #75.

Decisions

Same as #75, with these values:

• Settings mapping: rslint.enable → rstack.rslint.enable, rslint.corePath → rstack.rslint.corePath, rslint.trace.server → rstack.rslint.trace.server. rslint.binPath / rslint.customBinPath have no equivalent. Settings are not migrated automatically.
• Supported core range for the final release: @rslint/core ^0.9.0 (0.9.x prereleases included).
• displayName becomes Rslint (moved to Rstack). Do not try Rslint (Deprecated); the Marketplace rejects display names close to an existing one (TSLint (deprecated)) at publish time. Fallback: Rslint (now part of Rstack).
• No changes to rstack.rstack. No extensionPack / extensionDependencies link. "Don't show again" lives in globalState.

Final release behavior

Same three cases as #75, in order. Reference implementation: web-infra-dev/rstest packages/vscode/src/migrationNotice.ts and versionCheck.ts (web-infra-dev/rstest#1917).

1. rstack.rstack is installed and enabled. Stand down. Prompt "Rstack has taken over Rslint. Uninstall the Rslint extension." with Uninstall Rslint and Don't show again. Only check whether Rstack is installed; drop the current rstack.rslint.enable condition.
2. The local @rslint/core does not satisfy ^0.9.0. Do not start a runtime for that core. Error on every activation: "Rslint has moved into the Rstack extension. The Rslint extension only supports @rslint/core ^0.9.0 (found X). Please install Rstack." with Install Rstack.
3. Only the old extension is present. Run normally. Prompt once: "Rslint has moved into the Rstack extension. The Rslint extension is deprecated and will not be updated. Please install Rstack." with Install Rstack and Don't show again.

At most one notification at a time: case 3 is shown only if case 2 did not fire.

Checklist

Phase 1: final rstack.rslint release (web-infra-dev/rslint)

Upstream coverage after this phase: rstackjs/rstack-ecosystem-ci#104 runs this repo's test:unit against the freshly built @rslint/core on every rslint main push, once web-infra-dev/rslint#2420 connects rslint to the ecosystem CI. Unlike the Rstest suite (rstackjs/rstack-ecosystem-ci#99), it does not run lint yet. Renovate's rstack toolchain group, which includes @rslint/**, opens a PR that runs the three-platform E2E on every release. Running this repo's VS Code E2E in ecosystem-ci stays out of scope for the same reasons as #75.

• Implement the three cases above, with unit and E2E tests (feat(vscode): prepare the final standalone extension release web-infra-dev/rslint#2427)
• Add the ^0.9.0 semver guard on the local @rslint/core, checked from package.json before any core module is loaded (feat(vscode): prepare the final standalone extension release web-infra-dev/rslint#2427)
• Rename displayName to Rslint (moved to Rstack) (feat(vscode): prepare the final standalone extension release web-infra-dev/rslint#2427)
• Add the settings key mapping table to packages/vscode-extension/README.md (feat(vscode): prepare the final standalone extension release web-infra-dev/rslint#2427)
• Release through the normal Release workflow (to_release: all, extension_type: official) to both Marketplace and Open VSX (0.10.0: Open VSX on 2026-10-31, Marketplace on 2026-11-02 after renewing RSLINT_VSCE_PAT and re-running the failed job)
• Freeze the extension version: exclude packages/vscode-extension/package.json from scripts/version.mjs, update .agents/skills/prepare-rslint-npm-release/SKILL.md, and add --skip-duplicate to both publish commands in scripts/publish-marketplace.mjs so later full releases do not fail on the frozen version Superseded: chore: remove the retired standalone VS Code extension web-infra-dev/rslint#2488 removes the extension directly, so there is no version left to freeze
• Merge ci: connect Rslint to ecosystem CI web-infra-dev/rslint#2420 so rslint main pushes dispatch the ecosystem CI (merged 2026-10-14; the first main push after it, feat(vscode): prepare the final standalone extension release web-infra-dev/rslint#2427, dispatched rstackjs/rstack-ecosystem-ci with the rstack-editor suite from feat(rslint): add rstack-editor ecosystem suite rstack-ecosystem-ci#104)
• Remove the extension E2E from CI (test-node via the root test filter, and test-vscode-windows): it runs against the workspace @rslint/core, so the ^0.9.0 guard would fail it at the first 0.10.0 bump (ci: stop testing the retired standalone VS Code extension web-infra-dev/rslint#2480)

Phase 2: registries and docs (2 to 4 weeks after Phase 1)

• Request Marketplace deprecation (rstack.rslint → rstack.rstack, disallowInstall: false) in Deprecated extensions microsoft/vscode-discussions#1 (comment, requested 2026-11-02, not yet applied)
• Open a PR to EclipseFdn/publish-extensions extension-control/extensions.json with the same entry (Deprecate rstack.rslint in favour of rstack.rstack EclipseFdn/publish-extensions#1207, open)
• Replace remaining rstack.rslint references in rslint docs, templates, and .vscode/extensions.json files (the rslint repo's own references are handled in chore: remove the retired standalone VS Code extension web-infra-dev/rslint#2488, open)

Phase 3: stop publishing in rslint

• Remove the publish-extension-vscode and publish-extension-open-vsx jobs from .github/workflows/release.yml and the extension option of to_release (chore: remove the retired standalone VS Code extension web-infra-dev/rslint#2488, open)
• Revoke RSLINT_VSCE_PAT / RSLINT_OVSX_PAT

Phase 4: remove the source (brought forward: not waiting for installs to drop off)

• git rm -r packages/vscode-extension, then clean up the remaining references (root package.json filters and typecheck reference, tsconfig.json, cspell.config.cjs, rslint.config.ts, rstack.config.mts, .github/workflows/ci.yml, scripts/publish-marketplace.mjs, the release-prep skill) (chore: remove the retired standalone VS Code extension web-infra-dev/rslint#2488, open)
• Update both deprecation entries to disallowInstall: true (not yet: Phase 2 entries do not exist, and this should wait until installs have dropped off)

References

• Rstest extension sunset checklist #75 (Rstest sunset)
• Deprecating extensions: https://code.visualstudio.com/api/working-with-extensions/publishing-extension#deprecating-extensions
• Marketplace deprecation requests: Deprecated extensions microsoft/vscode-discussions#1
• Open VSX extension control: https://github.com/EclipseFdn/open-vsx.org/wiki/Managing-Extensions