Release

Release Workflow

Full doc: contributing/publishing.md

Scripts in this skill

From repo root (no global ts-node):

• npx ts-node .claude/skills/release/detect-state.ts — outputs JSON with currentRelease, version, priorRelease, tagExists, onReleaseBranch, commitCount, branchUrl, compareUrl

Step 0 — Verify Wednesday stable build

Run detect-state.ts first.

Note: createReleaseBranch.yml deprecated — use build-release.yml. Old workflow scheduled for deletion after proven stability (W-23988524).

Check scheduled build-release.yml ran Wednesday:

gh run list --workflow=build-release.yml -L 5 --repo forcedotcom/salesforcedx-vscode

Report status + timestamp. On failure, inspect logs:

gh run view <runId> --repo forcedotcom/salesforcedx-vscode

Decision matrix:

• Build succeeded → GitHub pre-release created w/ VSIX + SHA256. Continue to Step 1.
• Build failed → check logs. Issues: no marketplace prerelease (wait Wed 7 AM UTC) or build script error. Re-run:

  gh workflow run build-release.yml --repo forcedotcom/salesforcedx-vscode
  

• No run this week → Either:
  • Wait (Wed 8 AM UTC)
  • Trigger manually:

  gh workflow run build-release.yml --repo forcedotcom/salesforcedx-vscode
  

After re-dispatch, watch until complete:

gh run list --workflow=build-release.yml -L 1 --json databaseId --repo forcedotcom/salesforcedx-vscode
gh run watch <databaseId> --repo forcedotcom/salesforcedx-vscode

Step 1 — Download stable release build

Get VSIX + SHA256 from GitHub pre-release created by build-release.yml. Release notes link to docs/release-testing-guide.md for full testing/publishing instructions:

gh release list --repo forcedotcom/salesforcedx-vscode | head -5
gh release download v<version> \
  --dir ~/Downloads/v<version> \
  --pattern '*.vsix' \
  --repo forcedotcom/salesforcedx-vscode

Step 2 — Install and test locally

Ask user: code or code-insiders? (default code)

find ~/Downloads/v<version> -type f -name "*.vsix" -exec <binary> --install-extension {} \;

User should reload VS Code and run a few commands to validate.

Step 3 — Confirm manual testing is complete

3a — Create the Slack testing doc

The user creates the testing doc from the team's Slack template: https://salesforce.enterprise.slack.com/docs/T092Z56AE/F0B7RLRUSRG

Create a new doc from the Slack template and name it Release Testing v<version> (e.g. Release Testing v67.12.0), where <version> matches the GH release tag.

Use the version from Step 1. Wait for the user to confirm the doc is created and shared with the team before continuing.

3b — Run smoke checks

Tell the user: "Let me know when you've finished manually testing the installed vsixes (logged in the Slack doc) and you're ready to publish to the Microsoft Marketplace and Open VSX."

Suggested smoke checks the user may run before confirming:

• Authorize an org / set a default org
• Deploy and retrieve metadata
• Run an Apex test from the Test Explorer
• Open SOQL Builder and run a query
• Open the Org Browser

Do not proceed until the user explicitly confirms testing is complete.

Step 4 — Trigger marketplace publish

Once user confirms testing is complete, automatically trigger publishVSCode.yml with version (e.g., 67.12.0):

gh workflow run publishVSCode.yml -f releaseVersion=<version> --repo forcedotcom/salesforcedx-vscode

Triggers publishOpenVSX.yml. Both gated by publish environment — user will approve in GitHub UI (Actions → run → Review pending → Approve + deploy).

Tell user: "Triggered publish workflows. You'll need to approve the environment gates in GitHub Actions UI."

Monitor runs:

gh run list --workflow=publishVSCode.yml -L 1 --json databaseId,status,url --repo forcedotcom/salesforcedx-vscode
gh run watch <databaseId> --repo forcedotcom/salesforcedx-vscode

Verify live:

• Microsoft Marketplace
• Open VSX

Step 5 — Slack post

Compose from packages/salesforcedx-vscode/CHANGELOG.md (top section). Format:

• Header: *Salesforce Extensions for VS Code v<version> is out* :tada:
• Link: <https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode|VS Code Marketplace> → "see Changelog tab"
• Sections: *Added* / *Fixed*
• Subsections (#### foo) → blockquote (> foo)
• Drop PR/issue trailers

Show composed post. If Slack MCP available → offer to post/draft to #platform-dev-tools. Wait for approval before sending.

Emergency Hotfixes

For critical security/production bugs, use the separate /patch-release skill.

See patch-release/SKILL.md for emergency patch release workflow.

Conventions

• All gh commands use --repo forcedotcom/salesforcedx-vscode
• Don't approve publishes until manual testing done
• Patch releases bypass timeline for emergencies only
• Always cherry-pick fixes to develop after publishing