Update version to 2.5.0 (#720)

Update version to 2.4.5 (#718)

Update version to 2.4.0 (#710)

publish_npm: use Trusted Publishing (OIDC) for auth, not NPM_TOKEN (#700

)

Trusted Publishing is now configured on npmjs.org for theengs-decoder
(repo: theengs/decoder, workflow: publish_npm.yml). The v2.3.0 publish
still returned 404 because:

- Node 20 ships with npm 10.x, which only uses OIDC for provenance
  attestation. Authentication still relied on NODE_AUTH_TOKEN, and the
  NPM_TOKEN secret is no longer valid, so PUT was rejected.
- Full OIDC auth for npm publish requires npm 11.5.1+.

Upgrade npm to latest before publishing, and drop the NODE_AUTH_TOKEN
env from the publish steps so the CLI uses the Trusted Publisher flow
end-to-end. The NPM_TOKEN secret can be removed from the repo once
this lands.

Co-authored-by: Florian <1technophile@users.noreply.github.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Update version to 2.2.0 (#693)

Update version to 2.1.0 (#688)

Update version to 2.0.0 (#674)

Update version to 1.9.9 (#649)

Update version to 1.9.8 (#645)

Update version to 1.9.7 (#643)