Skip to content

V0.23 release#2032

Open
ArthurZucker wants to merge 3 commits intomainfrom
v0.23-release
Open

V0.23 release#2032
ArthurZucker wants to merge 3 commits intomainfrom
v0.23-release

Conversation

@ArthurZucker
Copy link
Copy Markdown
Collaborator

Draft PR

@HuggingFaceDocBuilderDev
Copy link
Copy Markdown

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@ArthurZucker ArthurZucker marked this pull request as ready for review April 27, 2026 13:53
ArthurZucker and others added 2 commits April 28, 2026 00:26
Lets us re-cut the npm publish independently of the python/rust
release workflows (which own `v*` and already created the GitHub
Release for 0.23.1, causing `napi prepublish` to 422 on retry).

- trigger: `v*` -> `node-v*`
- split publish into two steps:
  - `napi prepublish -t npm --no-gh-release` does the per-platform
    `npm publish` from `npm/<triple>/`, skipping the `POST /releases`
    call.
  - `npm publish --ignore-scripts` publishes the parent package
    without re-running the `prepublishOnly` hook.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Set napi.packageName so per-platform sub-packages publish as
`@huggingface/tokenizers-<triple>` (e.g. @huggingface/tokenizers-darwin-x64)
instead of unscoped `tokenizers-<triple>`.

The unscoped names on npm are owned by `n1t0` (Anthony Moi) — the org
CI npm token has no publish access there, which is why the 0.23.1
release attempt 404'd on the very first sub-package. The unscoped
sub-packages were never successfully published from CI; the only
versions on the registry (0.13.4-rc1/rc2) were hand-published by
n1t0 and the 0.13.3 stable parent shipped with optionalDependencies
that 404 at install (npm tolerates it for optionalDependencies).

Parent package stays `tokenizers` — public-facing import name is
unchanged. napi regenerates the runtime loader to require the
scoped names.

Also delete the 13 checked-in `bindings/node/npm/<triple>/` template
files. They hardcoded the old unscoped name and version 0.13.4-rc1
and were misleading as source. CI regenerates them via `napi
create-npm-dirs` (already in node-release.yml line 213).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants