[rahul-contentstack]

Why

0.3.9 wasn't published after #14 merged: npm publish failed with 401 Unauthorized because the PKG_TOKEN secret has expired.

What

Switches publish-epicurus-package.yml to the standard GitHub Packages publish workflow (Confluence: Packages | Publish | NPM):

• Trigger: release: [published] instead of every push to master
• Auth: github.token with permissions: packages: write instead of PKG_TOKEN
• Checks out the release tag; actions/checkout@v4 / actions/setup-node@v4, Node 24
• Still runs npm run compile before npm publish

Review notes

• Touches .github/workflows/, so it needs approval from @contentstack/security-admin.
• npm install -g npm@latest is unpinned (taken as-is from the standard workflow).

After merge

Create a GitHub Release with tag v0.3.9 on master to trigger the publish.

🤖 Generated with Claude Code

[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]

🔒 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	0	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

✅ BUILD PASSED - All security checks passed

[cs-bala]

LGTM!