Skip to content

refactor: migrate packaging to pyproject.toml - #106

Merged
JarbasAl merged 1 commit into
devfrom
fix/modernize-release-workflow
Jun 20, 2026
Merged

refactor: migrate packaging to pyproject.toml#106
JarbasAl merged 1 commit into
devfrom
fix/modernize-release-workflow

Conversation

@JarbasAl

@JarbasAl JarbasAl commented Jun 20, 2026

Copy link
Copy Markdown
Member

Migrate packaging to pyproject.toml (PEP 621) and drop setup.py, requirements*.txt, and MANIFEST.in.

This also fixes the broken alpha release that kept merged dep-cap fixes (e.g. ovos-bus-client<3.0.0) from publishing: the old workflow used TigreGotico/...publish-alpha.yml@master with an inline python setup.py sdist bdist_wheel that failed on the py3.14 runner (ModuleNotFoundError: setuptools). Now uses the standard OpenVoiceOS/...publish-alpha.yml@dev + python -m build.

Verified locally: uv build --wheel succeeds, console scripts and bundled res/ resources are present, version resolves dynamically from version.py.

🤖 Generated with Claude Code

The release used TigreGotico/gh-automations/publish-alpha.yml@master with inline 'python setup.py sdist bdist_wheel' on Python 3.14, failing with ModuleNotFoundError: setuptools — so every alpha release failed and merged dep fixes (ovos-bus-client<3.0.0) never reached PyPI. Switched to the standard OpenVoiceOS/gh-automations/publish-alpha.yml@dev (reads version from version.py, builds with python -m build), matching ovos-audio.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added the fix label Jun 20, 2026
@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@JarbasAl, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 8 minutes and 31 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: bf4cb74d-aa0b-43fc-aa73-9c3662018deb

📥 Commits

Reviewing files that changed from the base of the PR and between 289c6f1 and 018542f.

📒 Files selected for processing (1)
  • .github/workflows/release_workflow.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/modernize-release-workflow

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

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

@JarbasAl
JarbasAl marked this pull request as ready for review June 20, 2026 16:29
@JarbasAl
JarbasAl merged commit 674ea23 into dev Jun 20, 2026
3 of 4 checks passed
@JarbasAl
JarbasAl deleted the fix/modernize-release-workflow branch June 20, 2026 16:29
@JarbasAl JarbasAl changed the title fix: modernize release workflow to shared publish-alpha refactor: migrate packaging to pyproject.toml Jun 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant