chore(release): migrate to release-please

[angelxmoreno]

Summary by CodeRabbit

• Chores

  • Switched release automation to Release Please; removed the previous release automation and related release tooling/dependencies.
  • Bumped the release manifest version and enabled version tags that include the "v" prefix.

• Documentation

  • Updated release and maintenance docs to reflect the new PR-based release flow, token handling, changelog generation, and automated maintenance notes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Replaces semantic-release with Release Please: deletes the semantic-release workflow and config, removes related package.json scripts and devDependencies, adds/updates Release Please config and manifest, updates README and CHANGELOG references, and bumps the release manifest version.

Changes

Cohort / File(s)	Summary
Removed semantic-release workflow .github/workflows/release.yml	Deleted GitHub Actions workflow that ran semantic-release (checkout, setup Bun/Node, install, test, build, semantic-release).
Removed semantic-release config .releaserc.json	Deleted semantic-release configuration (branches, tag format, plugins: commit-analyzer, release-notes-generator, changelog, npm, github, git).
Package metadata and deps package.json	Removed release script (semantic-release) and removed semantic-release-related devDependencies (all @semantic-release/* packages and semantic-release).
Release Please config & manifest release-please-config.json, .release-please-manifest.json	Added include-v-in-tag: true to release-please-config.json. Bumped manifest entry version from 2.0.0 to 2.2.0 in .release-please-manifest.json.
Docs and changelog README.md, CHANGELOG.md	README updated to describe Release Please PR-based workflow, token/CI notes, and maintenance automation; CHANGELOG header text changed to reference Release Please instead of semantic-release.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Pay attention to:
  • release-please-config.json option semantics and compatibility with repository tagging policy.
  • .release-please-manifest.json version bump correctness and consistency with any package versions.
  • Removal of .releaserc.json and CI workflow: verify no other automation relies on semantic-release artifacts.
  • package.json script and devDependency removals for accidental dependency regressions.

Possibly related PRs

• feat: migrated to semantic release #8 — Reverses the earlier addition of semantic-release; touches the same release workflow and deps.
• feat!: made refactoring with breaking changes cause a major bump #13 — Modifies .releaserc.json (commit-analyzer) and therefore relates to changes removing that file.
• Feat/release please #17 — Also migrates release automation toward Release Please and updates manifest/workflow files.

Suggested labels

released

Poem

🐰 I hopped through CI with a cheer,
swapped old releases for a brand new gear.
Tags get a "v", the manifest grew,
changelogs whisper "Release Please" too. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title 'chore(release): migrate to release-please' directly describes the main objective of the changeset—migrating the release automation from semantic-release to release-please—which is confirmed by all the modifications across workflow files, configuration, and documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/release-please

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a3b147b and e80e30f.

📒 Files selected for processing (2)

• .release-please-manifest.json (1 hunks)
• package.json (0 hunks)

💤 Files with no reviewable changes (1)

• package.json

🚧 Files skipped from review as they are similar to previous changes (1)

• .release-please-manifest.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.42%. Comparing base (4a36072) to head (e80e30f).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #23   +/-   ##
=======================================
  Coverage   99.42%   99.42%           
=======================================
  Files           3        3           
  Lines         174      174           
=======================================
  Hits          173      173           
  Misses          1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c5719c3 and a3b147b.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (7)

• .github/workflows/release.yml (0 hunks)
• .release-please-manifest.json (1 hunks)
• .releaserc.json (0 hunks)
• CHANGELOG.md (1 hunks)
• README.md (1 hunks)
• package.json (1 hunks)
• release-please-config.json (1 hunks)

💤 Files with no reviewable changes (2)

• .releaserc.json
• .github/workflows/release.yml

🧰 Additional context used

🧠 Learnings (5)

📚 Learning: 2025-12-17T08:35:10.837Z

Learnt from: CR
Repo: angelxmoreno/sneakerdb-client PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-17T08:35:10.837Z
Learning: Applies to src/**/*.ts : Source TypeScript files should be organized in `src/` directory with `TheSneakerDatabaseClient.ts` exposing the SDK, `interfaces.ts` for shared types, `utils.ts` for helpers, and `index.ts` re-exporting public modules

Applied to files:

• package.json

📚 Learning: 2025-12-17T08:35:10.838Z

Learnt from: CR
Repo: angelxmoreno/sneakerdb-client PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-17T08:35:10.838Z
Learning: Run `bun run build` to execute Bun bundling and `tsc --emitDeclarationOnly` into `dist/`

Applied to files:

• package.json

📚 Learning: 2025-12-17T08:35:10.838Z

Learnt from: CR
Repo: angelxmoreno/sneakerdb-client PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-17T08:35:10.838Z
Learning: Enforce Biome formatting and linting using `bun run lint` and `bun run lint:fix` commands

Applied to files:

• package.json

📚 Learning: 2025-12-17T08:35:10.838Z

Learnt from: CR
Repo: angelxmoreno/sneakerdb-client PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-17T08:35:10.838Z
Learning: Target Node 20+ or Bun 1.2+ with TypeScript strict rules enforced by Biome's defaults using the `universe` preset

Applied to files:

• package.json

📚 Learning: 2025-12-17T08:35:10.838Z

Learnt from: CR
Repo: angelxmoreno/sneakerdb-client PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-17T08:35:10.838Z
Learning: Include linked issues and screenshots for README changes in pull requests and mention configuration shifts and request review after CI passes

Applied to files:

• README.md

🔇 Additional comments (4)

CHANGELOG.md (1)

81-81: LGTM!

The changelog header correctly reflects the migration to Release Please. The warning about automatic generation is standard and appropriate.

release-please-config.json (1)

2-2: LGTM!

The include-v-in-tag setting is correctly configured to ensure version tags follow the vX.Y.Z format, which is a standard convention for npm packages.

package.json (1)

42-70: Clean migration from semantic-release dependencies.

The removal of the release script and all semantic-release related devDependencies is correct and complete. The remaining dependencies and scripts are appropriate for the Release Please workflow.

README.md (1)

70-72: No action needed. The .github/workflows/release-please.yml workflow file exists and is properly configured with GITHUB_TOKEN. The README documentation accurately reflects the workflow behavior.

Likely an incorrect or invalid review comment.