Pump to 2.1.1 (#1563)

Fix: #1562

Pump to 2.1.0 (#1547)

Fix: #1540

Pump to 2.1.0 (#1547)

Fix: #1540

Pump to 2.1.0-beta.0 pre-release (#1536)

Fix: #1535

Pump to 2.0.0 (#1517)

Fix: #1458

Pump to 2.0.0 (#1517)

Fix: #1458

Trigger npm-publish on prerelease tags (#1501)

Commit e54a991 (#1490) tightened the tag filter from `'*'` to `'[0-9]+.[0-9]+.[0-9]+'`, which only matches plain `MAJOR.MINOR.PATCH` tags. Prerelease tags such as `2.0.0-beta.0` no longer trigger the workflow, even though `1.9.0-alpha.0` published successfully under the previous pattern.

Restore prerelease support by adding a second pattern `'[0-9]+.[0-9]+.[0-9]+-*'` alongside the existing one, so tags like `2.0.0-beta.0`, `1.9.0-alpha.0`, and `2.0.0-rc.1` trigger the workflow while unrelated tags (e.g. `docs-*`) remain excluded.

Fix: #1500

Pump to 1.9.0 (#1476)

Fix: #1475

Support pre-release publishing in npm-publish workflow (#1464)

Add automatic dist-tag detection to the publish step. npm requires `--tag` when publishing pre-release versions to prevent them from becoming the default `latest` on the registry.

The new `Determine dist-tag` step reads the version from `package.json` and extracts the pre-release label (e.g. `alpha`, `beta`, `rc`) if present, otherwise defaults to `latest`. This tag is passed to `npm publish --tag`.

Examples:
- `1.9.0-alpha.0` → `--tag alpha`
- `1.9.0-beta.1` → `--tag beta`
- `1.9.0-rc.0` → `--tag rc`
- `1.9.0` → `--tag latest`

Fix: #1459

Pump to 1.8.3 (#1426)