feat: updated release workflow to automatically create a tag & release

[jurerotar]

No description provided.

[jurerotar]

Hmmm, seems to still be failing. Can we check npmjs.org config whether workflows may do releases?

[tomayac]

npm notice
npm notice 📦  @sqlite.org/sqlite-wasm@3.53.4-build1
npm notice Tarball Contents
npm notice 6.6kB README.md
npm notice 297.2kB dist/index.d.mts
npm notice 642.7kB dist/index.mjs
npm notice 537.8kB dist/node.mjs
npm notice 32.5kB dist/sqlite3-opfs-async-proxy.js
npm notice 635.9kB dist/sqlite3-worker1.mjs
npm notice 868.9kB dist/sqlite3.wasm
npm notice 2.9kB package.json
npm notice Tarball Details
npm notice name: @sqlite.org/sqlite-wasm
npm notice version: 3.53.4-build1
npm notice filename: sqlite.org-sqlite-wasm-3.53.4-build1.tgz
npm notice package size: 977.6 kB
npm notice unpacked size: 3.0 MB
npm notice shasum: 796d941a63ef274b220cb709dcba74cc432abdd7
npm notice integrity: sha512-U8pvL0patYHMg[...]VG453ixnxBOnA==
npm notice total files: 8
npm notice
npm notice npm tokens that bypass 2FA are being restricted for account changes and direct publishing. Learn how to prepare: https://gh.io/npm-gat-bypass2fa-deprecation
npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm notice publish Signed provenance statement with source and build information from GitHub Actions
npm notice publish Provenance statement published to transparency log: https://search.sigstore.dev/?logIndex=2756203284
npm error code E404
npm error 404 Not Found - PUT https://registry.npmjs.org/@sqlite.org%2fsqlite-wasm - Not found
npm error 404
npm error 404  The requested resource '@sqlite.org/sqlite-wasm@3.53.4-build1' could not be found or you do not have permission to access it.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-09-08T09_33_13_130Z-debug-0.log

Is the %2f expected in https://registry.npmjs.org/@sqlite.org%2fsqlite-wasm?

[jurerotar]

I think this is a problem on npm side. This is the first time we ran this workflow and we probably haven't set up the trusted publisher. Should look something like this in the end:

[tomayac]

Where should this UI appear?

[jurerotar]

Try https://www.npmjs.com/package/@sqlite.org/sqlite-wasm/access 😄

[tomayac]

Still no luck, but it looks correct:

Am I missing something somewhere?

[jurerotar]

I think it should be set to publish.yml, instead of the build-wasm.yml

[tomayac]

Changing the name did the trick. Who could've thunk ;-) Good catch!

[jurerotar]

I’m just glad I didn’t need to update the workflow for the third time 😆

We also have that nice provenance section now: https://www.npmjs.com/package/@sqlite.org/sqlite-wasm

In any case, I’ll monitor future SQLite releases and will do my best to publish a new release when upstream does so as well 😄

[tomayac]

Fantastic, thanks for the hard work! <3