Update release workflow to use trusted publishing

[risantos]

Description

• Updates the release workflow to use OIDC publishing via release-it. See https://github.com/release-it/release-it/blob/3378faf75f1a8e2e87f63a4914f8df68223b3a5b/docs/npm.md#trusted-publishing-oidc

[Copilot]

Pull request overview

This PR updates the release workflow to use OIDC-based trusted publishing for npm, which is more secure than using long-lived tokens. The changes include upgrading release-it to version 19.2.3, updating GitHub Actions to v6, and configuring the workflow with the necessary id-token: write permission.

Changes:

• Updated release-it from 19.0.3 to 19.2.3 to support OIDC publishing
• Configured GitHub workflow with OIDC permissions (id-token: write)
• Updated GitHub Actions to v6 and Node.js to version 24
• Removed manual npm token configuration in favor of automatic OIDC authentication
• Added skipChecks: true to npm publishing configuration

Reviewed changes

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

File	Description
package.json	Updated release-it dependency from ^19.0.3 to ^19.2.3
.release-it.js	Added skipChecks: true to npm configuration
.github/workflows/release.yaml	Updated to use OIDC authentication with id-token permission, upgraded actions to v6, and Node.js to v24
yarn.lock	Updated all transitive dependencies from release-it and related packages

---

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

[Copilot]

Upgrading from Node.js 22 to Node.js 24 is a significant version change. Node.js 24 was released in October 2024 and may not be LTS yet. Verify that all dependencies and tooling in this project are compatible with Node.js 24, or consider using Node.js 22 LTS or Node.js 20 LTS for stability.

Suggested change

	node-version: 24
	node-version: 22.x

[Copilot]

The skipChecks: true option bypasses important npm pre-publish checks. This setting should only be used if there's a specific reason to skip npm's built-in validation. Consider documenting why this is necessary or removing it to maintain standard npm publishing safety checks.

Suggested change

	publish: true,
	skipChecks: true
	}
	};
	publish: true
	}
	};