fix: npm publish

[patriksimek]

No description provided.

[Copilot]

Pull request overview

This PR updates the package metadata and GitHub Actions workflow to improve npm publish reliability (including provenance) and refresh Node versions used in CI/publish.

Changes:

• Bump package version to 0.10.2 and switch repository to the object form expected by some tooling.
• Expand CI test matrix to include Node 24.
• Update publish job permissions and publish command to include npm --provenance.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 3 comments.

File	Description
package.json	Bumps version and adjusts repository metadata format for npm publication.
.github/workflows/deploy-npm.yml	Updates Node versions, adds OIDC permissions, and enables provenance for npm publish.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

node-version is typically provided as a string (and you already use strings in the matrix). Leaving it unquoted makes YAML treat it as a number, which can lead to subtle formatting/coercion issues. Consider using quotes for consistency, e.g. node-version: '24'.

Suggested change

	node-version: 24
	node-version: '24'

[Copilot]

The Node version is defined in two places (matrix and publish job), and they’re currently inconsistent in representation (string list vs numeric). To avoid drift (e.g., bumping the matrix but forgetting publish), consider centralizing the publish Node version (e.g., via an env value reused in both places) or making publish run on a matrix entry.

[Copilot]

The Node version is defined in two places (matrix and publish job), and they’re currently inconsistent in representation (string list vs numeric). To avoid drift (e.g., bumping the matrix but forgetting publish), consider centralizing the publish Node version (e.g., via an env value reused in both places) or making publish run on a matrix entry.