fix(release): use default versioning strategy for release-please

[polaz]

Summary

• Change "versioning": "semver" to "versioning": "default" in release-please-config.json

Problem

Release Please v17 removed the semver versioning strategy type. The workflow was failing immediately after the PR #2 merge with:

Error: Unknown versioning strategy type: semver

The correct value is default (which implements semver behaviour in v17+).

Test Plan

• release-please.yml workflow completes without errors on next push to main

Closes #3

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 573f3ab2-2f78-4d23-b993-744420bd8e26

📥 Commits

Reviewing files that changed from the base of the PR and between 2462cb9 and ad8b121.

📒 Files selected for processing (1)

• release-please-config.json

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated release versioning configuration to use default versioning strategy.

Walkthrough

The release-please-config.json file was updated to change the versioning strategy from "semver" to "default" in response to Release Please v17 removing support for the semver strategy type. The default strategy implements semver behavior in v17+.

Changes

Cohort / File(s)	Summary
Configuration Update release-please-config.json	Updated versioning strategy from "semver" to "default" to comply with Release Please v17 breaking changes that removed the semver strategy type.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating the release-please configuration to use the default versioning strategy instead of semver.
Description check	✅ Passed	The description is directly related to the changeset, explaining the problem (Release Please v17 removed semver support), the solution (use default strategy), and the test plan.
Linked Issues check	✅ Passed	The pull request addresses all objectives from issue #3: changes versioning from semver to default, resolves Release Please v17 compatibility, and includes test plan for validation.
Out of Scope Changes check	✅ Passed	All changes are in-scope: only the versioning strategy in release-please-config.json is modified, directly addressing the issue #3 requirements.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/#3-release-please-versioning

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud