Repository navigation
chore: bootstrap releases for path: . - #574
Conversation
WalkthroughIntroduces release-please configuration by adding two root-level files: Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
| { | ||
| ".": "0.0.0" | ||
| } No newline at end of file |
There was a problem hiding this comment.
Set manifest to the real last released version
Setting the root to 0.0.0 tells release-please that the most recent release was 0.0.0, so the very next PR will try to tag a brand-new 0.x version and ignore the existing 4.x history. Please seed the manifest with the actual current version (today that’s 4.8.1) so the generated release cadence stays aligned with what’s already on PyPI. (github.com)
Apply this diff to fix the initial version:
- ".": "0.0.0"
+ ".": "4.8.1"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| { | |
| ".": "0.0.0" | |
| } | |
| { | |
| ".": "4.8.1" | |
| } |
🤖 Prompt for AI Agents
In .release-please-manifest.json around lines 1 to 3 the manifest seeds the root
version as "0.0.0", which will make release-please ignore existing 4.x history;
update the manifest to the actual last released version by replacing "0.0.0"
with "4.8.1" so future releases continue from the correct version.
| "packages": { | ||
| ".": { | ||
| "changelog-path": "CHANGELOG.md", | ||
| "bump-minor-pre-major": false, | ||
| "bump-patch-for-minor-pre-major": false, | ||
| "draft": false, | ||
| "prerelease": false | ||
| } |
There was a problem hiding this comment.
Declare the Python release strategy
Without an explicit release-type, release-please defaults this component to node, which will skip all of the Python-version bumping logic and leave files like pyproject.toml untouched. Add the Python release type (and the matching package name) so the bot edits the correct artifacts. (github.com)
Apply this diff to align the configuration with the Python SDK:
- ".": {
+ ".": {
+ "release-type": "python",
+ "package-name": "deepgram-sdk",
"changelog-path": "CHANGELOG.md",
"bump-minor-pre-major": false,
"bump-patch-for-minor-pre-major": false,
"draft": false,
"prerelease": false📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "packages": { | |
| ".": { | |
| "changelog-path": "CHANGELOG.md", | |
| "bump-minor-pre-major": false, | |
| "bump-patch-for-minor-pre-major": false, | |
| "draft": false, | |
| "prerelease": false | |
| } | |
| "packages": { | |
| ".": { | |
| "release-type": "python", | |
| "package-name": "deepgram-sdk", | |
| "changelog-path": "CHANGELOG.md", | |
| "bump-minor-pre-major": false, | |
| "bump-patch-for-minor-pre-major": false, | |
| "draft": false, | |
| "prerelease": false | |
| } |
🤖 Prompt for AI Agents
In release-please-config.json around lines 2 to 9, the package entry lacks a
release-type and package-name so release-please defaults to node and won't
update Python artifacts; add "release-type": "python" and "package-name":
"<your-python-package-name>" (replace with the actual PyPI/package identifier
used in pyproject.toml) to the "." package object so the releaser runs
Python-specific bumping and edits pyproject.toml and other Python files.
1 participant
Configuring release-please for path: .
Summary by CodeRabbit
New Features
Chores
Notes