Skip to content

ci: rename publish.yml to publish-py.yml - #688

Merged
pratyush618 merged 1 commit into
masterfrom
chore/rename-publish-py
Aug 17, 2026
Merged

ci: rename publish.yml to publish-py.yml#688
pratyush618 merged 1 commit into
masterfrom
chore/rename-publish-py

Conversation

@kartikeya-27

@kartikeya-27 kartikeya-27 commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Brings the Python release workflow in line with its four siblings — publish-crates.yml, publish-node.yml, publish-java.yml, publish-server.yml — which all name their registry. Pure rename: contents, triggers (1.0.0 / v1.0.0 tags), and the pypi environment are unchanged.

The publish-node.yml header comment carried a cross-reference to the old filename. The reference is dropped rather than repointed — the comment reads fine without naming another workflow.

Register the PyPI trusted publisher against the new filename. PyPI matches the workflow by file name, and flexiq has no publisher configured yet, so the pending publisher must read:

PyPI Project Name:  flexiq
Owner:              ByteVeda
Repository name:    flexiq
Workflow name:      publish-py.yml
Environment name:   pypi

Registering publish.yml instead would fail at publish time.

@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@kartikeya-27, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 50 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

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 reviews.

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e94519ee-9e5f-4abb-8712-c9c0630e8659

📥 Commits

Reviewing files that changed from the base of the PR and between 0b778b2 and a0197b0.

📒 Files selected for processing (2)
  • .github/workflows/publish-node.yml
  • .github/workflows/publish-py.yml

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.

@kartikeya-27
kartikeya-27 force-pushed the chore/rename-publish-py branch from ebe9332 to a0197b0 Compare August 17, 2026 19:14
@github-actions github-actions Bot added the ci label Aug 17, 2026
@pratyush618
pratyush618 merged commit ef8ddcd into master Aug 17, 2026
19 checks passed
@pratyush618
pratyush618 deleted the chore/rename-publish-py branch August 17, 2026 19:19
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.

2 participants