fix: poetry release ci

[leehuwuj]

Summary by CodeRabbit

• Chores
  • Improved release workflow safeguards to avoid unintended triggers.
  • Streamlined the process for capturing the current version and publishing, ensuring a more reliable package release.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 13660ec

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates the GitHub Actions workflow file for releasing the Llama Index server package. The modifications adjust the release job condition to prevent execution on branches starting with refs/heads/release/llama-index-server-v. It also removes the package build step, replacing it with a new step that retrieves the current package version, and updates the publish step to utilize the JRubics/poetry-publish@v2.1 action with specific parameters.

Changes

File(s)	Change Summary
.github/workflows/...release_llama_index_server.yml	- Conditional Execution: Updated the release job condition to include a branch prefix check. - Steps Modification: Removed the build package step and added a step to capture the package version using poetry version -s. - Publishing Update: Modified the publish step to use JRubics/poetry-publish@v2.1 with appropriate parameters.

Sequence Diagram(s)

sequenceDiagram
  participant GitHub as GitHub
  participant Workflow as Workflow
  participant VersionStep as Version Extraction
  participant Publisher as Publishing Action
  GitHub->>+Workflow: Push event triggers workflow
  Workflow->>Workflow: Check branch condition
  alt Branch allowed
      Workflow->>+VersionStep: Retrieve package version (poetry version -s)
      VersionStep-->>-Workflow: Version returned
      Workflow->>+Publisher: Execute publishing with JRubics/poetry-publish@v2.1
      Publisher-->>-Workflow: Publishing result
  else Branch disallowed
      Workflow-->>GitHub: Skip release job
  end

Loading

Possibly related PRs

• fix release CI: add --no-interaction #521: Modifies the "Publish to PyPI" step in the same workflow, aligning closely with the changes made in this PR.

Poem

I’m a rabbit hopped up on CI cheer,
Skipping branches that I need not fear.
No more build step, a version is my prize,
With publishing magic right before our eyes.
Hopping along the workflow trail,
This code update will never fail!
🐰💻

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fceec69 and 13660ec.

📒 Files selected for processing (1)

• .github/workflows/release_llama_index_server.yml (2 hunks)

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.