Skip to content

ci: migrate from release-please to semantic-release #146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
github-actions wants to merge 1 commit into
base: master
Choose a base branch
from
Open

ci: migrate from release-please to semantic-release #146

github-actions wants to merge 1 commit into from

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Dec 2, 2025

Recent Commits:

  • ci: migrate from release-please to semantic-release (4f19649)

This code was generated with the assistance of Claude AI.

@claude
ci: migrate from release-please to semantic-release
4f19649 
Replace Release Please with semantic-release for automated releases.
This changes the release workflow from batched release PRs to
per-commit automated releases.

Key changes:
- Install semantic-release and plugins (@semantic-release/changelog,
  @semantic-release/git, @semantic-release/github, @semantic-release/npm,
  @semantic-release/exec)
- Add .releaserc.json configuration with release rules
- Replace .github/workflows/release-please.yml with semantic-release.yml
- Remove release-please-config.json and .release-please-manifest.json
- Update all documentation (CLAUDE.md, README.md, MERGE_COMMIT_SETUP.md,
  GITHUB_ACTIONS_NOTES.md)
- Add SEMANTIC_RELEASE_GUIDE.md
- Remove RELEASE_PLEASE_MAINTAINER_GUIDE.md
- Remove .github/workflows/format-release-pr.yml (no longer needed)
- Update .github/labeler.yml to reference new config files

Release behavior changes:
- Every qualifying commit (feat, fix, perf, refactor) triggers immediate
  release
- Non-releasing types (docs, chore, ci, test, style) skip releases
- Version bumps: feat/fix/perf/refactor → patch, feat! → minor (pre-1.0)
- CHANGELOG.md auto-updated on each release
- npm publishing via Trusted Publishers (OIDC) with --provenance flag
- JSR publishing continues as before

For maintainers: See SEMANTIC_RELEASE_GUIDE.md for detailed workflow
documentation.
@socket-security
Copy link

socket-security bot commented Dec 2, 2025

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Added@​semantic-release/​changelog@​6.0.3991009084100
Added@​semantic-release/​git@​10.0.19910010084100
Added@​semantic-release/​exec@​7.1.010010010087100
Added@​semantic-release/​github@​12.0.29910010094100
Addedsemantic-release@​25.0.29810010097100
Added@​semantic-release/​npm@​13.1.29810010097100

View full report

@socket-security
Copy link

socket-security bot commented Dec 2, 2025

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm npm is 94.0% likely obfuscated

Confidence: 0.94

Location: Package overview

From: package.json → npm/@semantic-release/npm@13.1.2 → npm/npm@11.6.4

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npm@11.6.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

ai-generated claude-code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@claude