Release Guide

Maintainer flow for publishing @siisee11/discode and platform-specific binary packages. Adapted from docs/RELEASE_NPM.ko.md.

1) Pre-check

Confirm npm account has publish access under siisee11.
Use npm automation token if 2FA is enabled.
Never expose or commit npm tokens.

npm whoami
npm token list

2) Bump version

Update both:

package.json version
optionalDependencies versions for all @siisee11/discode-* packages

3) Build and package

npm run typecheck
npm run build
npm run build:release
npm run pack:release

Artifacts are generated under dist/release/.

4) Publish packages

Publish platform packages first, then publish the meta package.

npm publish --access public --workspaces=false dist/release/discode-darwin-arm64
npm publish --access public --workspaces=false dist/release/discode-darwin-x64
npm publish --access public --workspaces=false dist/release/discode-linux-x64
npm publish --access public --workspaces=false dist/release/discode-windows-x64

npm publish --access public --workspaces=false dist/release/npm/discode

Publish every generated platform package for your release. The list above is shortened for readability.

5) Verify release

npm view @siisee11/discode version
npm i -g @siisee11/discode@latest
discode --version

Common publish issues

EOTP: likely non-automation token or restrictive 2FA policy.
You cannot publish over the previously published versions: version already exists.
Access token expired or revoked: refresh npm auth token and retry.