chore(ci): update semantic-release to support OIDC workflow

[jhampton]

per latest documentation and
semantic-release/npm#958

Description

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation update
• refactor: Code refactoring (no functional changes)
• perf: Performance improvement
• test: Test additions or updates
• build: Build system or dependency changes
• ci: CI configuration changes
• chore: Other changes (maintenance, etc.)

Breaking Changes

• This PR contains BREAKING CHANGES

Breaking Change Details:

Migration Guide:

Checklist

• My code follows the project's code style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings or errors
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• All commit messages follow conventional commits format
• I have updated the appropriate section in documentation (if needed)

Conventional Commits

✅ All commits in this PR follow conventional commit format:

<type>(<scope>): <subject>

[optional body]

[optional footer]

Example commit messages:

• feat(api): add Bible verse lookup method
• fix(auth): resolve token refresh race condition
• docs: update installation instructions

For breaking changes:

• feat(api)!: redesign Bible content API

See CONTRIBUTING.md for detailed guidelines.

Related Issues

Closes #
Relates to #

Additional Context

Reviewer Notes

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[github-actions]

🎉 This PR is included in version 0.8.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[greptile-apps]

Greptile Summary

This PR upgrades semantic-release from v24.2.0 to v25.0.2 to enable OIDC-based NPM publishing workflow, as discussed in the referenced GitHub issue.

Key Changes:

• Upgraded semantic-release to v25.0.2 which includes @semantic-release/npm v13.1.3 with built-in OIDC support via @actions/core v2.0.0
• Removed empty dependencies field from package.json (cleanup)
• Updated transitive dependencies including @semantic-release/github (v11→v12), @semantic-release/npm (v12→v13), and related packages
• Node.js engine requirement increased to ^22.14.0 || >= 24.10.0 (already addressed in release workflow which uses Node 24)

Compatibility Notes:

• The existing semantic-release plugins (@semantic-release/changelog@6.0.3, @semantic-release/exec@6.0.3, @semantic-release/git@10.0.1) specify peerDependencies: "semantic-release": ">=18.0.0" and should remain compatible with v25
• The release workflow already uses Node.js 24 and has NPM_CONFIG_PROVENANCE: true enabled, meeting the new requirements
• The .releaserc.json already has provenance: true configured in the npm plugin settings

Confidence Score: 5/5

• This PR is safe to merge - straightforward dependency upgrade aligned with documented requirements
• The upgrade follows the official semantic-release v25 migration path for OIDC support. All necessary workflow configurations (Node 24, provenance flags) are already in place. The existing plugins remain compatible per their peer dependency ranges.
• No files require special attention

Important Files Changed

Filename	Overview
package.json	Updated semantic-release from v24.2.0 to v25.0.2 and removed empty dependencies field
package-lock.json	Lockfile updated with semantic-release v25 and new dependencies including @actions/core for OIDC support

Sequence Diagram

sequenceDiagram
    participant GHA as GitHub Actions
    participant SR as semantic-release v25
    participant NPM_Plugin as @semantic-release/npm v13
    participant Actions_Core as @actions/core
    participant NPM_Registry as NPM Registry
    
    GHA->>GHA: Set id-token: write permission
    GHA->>GHA: Set NODE_AUTH_TOKEN & NPM_CONFIG_PROVENANCE
    GHA->>SR: Run semantic-release
    SR->>SR: Analyze commits & generate version
    SR->>NPM_Plugin: Prepare package for publishing
    NPM_Plugin->>Actions_Core: Request OIDC token
    Actions_Core->>GHA: Get OIDC token from GitHub
    GHA-->>Actions_Core: Return OIDC token
    Actions_Core-->>NPM_Plugin: Provide OIDC token
    NPM_Plugin->>NPM_Registry: Publish with provenance (OIDC auth)
    NPM_Registry-->>NPM_Plugin: Package published with attestations
    NPM_Plugin-->>SR: Publishing complete
    SR->>SR: Create GitHub release & update changelog

Loading