npm auth fails when my account uses a passkey

I have an NPM account with a passkey for auth. When I run pnpm publish directly, it opens my browser to complete authentication, which works. When I try to make a release using repoplone, it fails asking for a TOTP:

05/08 Release frontend

Release failed: NPM publish failed - npm version
[32m✔[39m npm version
- node -e "const fs=require('fs');const m=JSON.parse(fs.readFileSync('../../mrs.developer.json','utf8'));if(!m.core||!m.core.tag){console.error('Missing mrs.developer core.tag');process.exit(1);}const 
p=JSON.parse(fs.readFileSync('package.json','utf8'));p.volto_version=m.core.tag;fs.writeFileSync('package.json',JSON.stringify(p,null,2)+'\n');"
[32m✔[39m node -e "const fs=require('fs');const m=JSON.parse(fs.readFileSync('../../mrs.developer.json','utf8'));if(!m.core||!m.core.tag){console.error('Missing mrs.developer core.tag');process.exit(1);}const 
p=JSON.parse(fs.readFileSync('package.json','utf8'));p.volto_version=m.core.tag;fs.writeFileSync('package.json',JSON.stringify(p,null,2)+'\n');"
- git add package.json
[32m✔[39m git add package.json
- pipx run towncrier build --draft --yes --version 2.0.0-alpha.16 > .changelog.draft
[32m✔[39m pipx run towncrier build --draft --yes --version 2.0.0-alpha.16 > .changelog.draft
- pipx run towncrier build --yes --version 2.0.0-alpha.16
[32m✔[39m pipx run towncrier build --yes --version 2.0.0-alpha.16
- cp ../../README.md ./ && cp CHANGELOG.md ../../CHANGELOG.md
[32m✔[39m cp ../../README.md ./ && cp CHANGELOG.md ../../CHANGELOG.md
- python3 -c 'import json; data = json.load(open("../../package.json")); data["version"] = "2.0.0-alpha.16"; json.dump(data, open("../../package.json", "w"), indent=2)'
[32m✔[39m python3 -c 'import json; data = json.load(open("../../package.json")); data["version"] = "2.0.0-alpha.16"; json.dump(data, open("../../package.json", "w"), indent=2)'
- git add ../../CHANGELOG.md ../../package.json
[32m✔[39m git add ../../CHANGELOG.md ../../package.json
- Publishing to npm...
[31m✖[39m Publishing to npm...
ERROR npm notice
npm notice 📦  @kitconcept/website@2.0.0-alpha.16
npm notice Tarball Contents
npm notice 33B .changelog.draft
npm notice 1.3kB .release-it.json
npm notice 2.8kB CHANGELOG.md
npm notice 4.6kB README.md
npm notice 322B babel.config.js
npm notice 249B locales/de/LC_MESSAGES/volto.po
npm notice 249B locales/en/LC_MESSAGES/volto.po
npm notice 715B locales/es/LC_MESSAGES/volto.po
npm notice 552B locales/pt_BR/LC_MESSAGES/volto.po
npm notice 471B locales/volto.pot
npm notice 0B news/.gitkeep
npm notice 3.0kB package.json
npm notice 0B src/components/.gitkeep
npm notice 349B src/components/Blocks/ContactList/schema.ts
npm notice 638B src/config/blocks.ts
npm notice 365B src/config/settings.ts
npm notice 288B src/index.ts
npm notice 4.4kB src/internalChecks.test.ts
npm notice 870B towncrier.toml
npm notice 961B tsconfig.json
npm notice Tarball Details
npm notice name: @kitconcept/website
npm notice version: 2.0.0-alpha.16
npm notice filename: kitconcept-website-2.0.0-alpha.16.tgz
npm notice package size: 7.3 kB
npm notice unpacked size: 22.2 kB
npm notice shasum: fb762e4ec12fed61a2aa49c3bc252375344f8f27
npm notice integrity: sha512-b/c74/Z0atjyG[...]02Ib/VHJY1TIg==
npm notice total files: 20
npm notice
npm notice Publishing to https://registry.npmjs.org/ with tag alpha and public access
npm error code EOTP
npm error This operation requires a one-time password from your authenticator.
npm error You can provide a one-time password by passing --otp=<code> to the command you ran.
npm error If you already provided a one-time password then it is likely that you either typoed
npm error it, or it timed out. Please try again.
npm error A complete log of this run can be found in: /Users/davisagli/.npm/_logs/2026-04-21T19_55_57_604Z-debug-0.log

Possibly we need to run release-it differently so that it has an interactive terminal.