chore(release): publish to npm with trusted publishing

[cs-raj]

Problem

npm-publish.yml publishes @contentstack/delivery-sdk to npm with a long-lived NPM_TOKEN.

The SE1 publishing policy requires OIDC trusted publishing instead: no token, a release.yml workflow that runs when a release is published, Node 24.

The GitHub Packages job also authenticates with a personal token (PKG_TOKEN) and lacks the packages: write permission.

Fix

npm-publish.yml is renamed to release.yml. What changes inside it:

	Before	After
Trigger	release: created	release: published
npm auth	NPM_TOKEN	OIDC — id-token: write, no token
npm publish	npm publish --tag latest --access public	npm publish --access public; pre-releases go to the beta dist-tag, releases to latest
GitHub Packages	PKG_TOKEN (personal token), no packages: write	github.token with packages: write
Node / npm	22.x / npm 10	24 / latest npm
Checkout	implicit, credentials persisted	the release tag, persist-credentials: false
Actions	checkout@v4, setup-node@v4	@v7
package.json	no repository field	names this repo (provenance validation requires it)

Verification

Node 22 and Node 24: install, build, tests and npm pack all pass.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	98.9%	993/1004
🟢	Branches	96.52%	305/316
🟢	Functions	97.79%	221/226
🟢	Lines	99.37%	945/951

Test suite run success

720 tests passing in 36 suites.

Report generated by 🧪jest coverage report action from 43f0338

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	0	25	✅ Passed
🟡 Medium Severity	0	2	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	0	90 / 365 days	✅ Passed
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 0
• Medium without fixes: 2
• Low without fixes: 0

✅ BUILD PASSED - All security checks passed

[Copilot]

Copilot review overview

🟡 Changes recommended

GitHub Packages currently promotes prereleases under the latest dist-tag.

Review effort: Balanced
Findings: 1

Open (1)

• Use prerelease-aware dist-tag for GitHub Packages publishing · New

What changed in this PR

Migrates package releases to OIDC trusted publishing and improves GitHub Packages authentication.

Changes:

• Replaces token-based npm authentication with OIDC.
• Uses Node 24 and release-aware npm dist-tags.
• Adds repository metadata for provenance validation.

File	Description
package.json	Adds repository metadata.
.github/​workflows/​release.yml	Introduces trusted publishing workflows.
.github/​workflows/​npm-publish.yml	Removes the legacy token-based workflow.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.