update release workflow for llama-index-server

[leehuwuj]

Summary by CodeRabbit

• Chores
  • Refined the publishing workflow to target the correct package source and optimize dependency management by excluding unnecessary development packages.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 33eaeaf

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

The pull request updates the GitHub Actions workflow for releasing the package. It removes the ignore_dev_requirements parameter and adds two new parameters, package_directory and poetry_install_options, to the publish step. These updates modify how the publishing step determines the package location and manages dependency installation by excluding development dependencies.

Changes

File	Change Summary
.github/workflows/release_llama_index_server.yml	Removed the ignore_dev_requirements parameter; added package_directory: "llama-index-server" and poetry_install_options: "--without dev" in the publish step.

Sequence Diagram(s)

sequenceDiagram
    participant Workflow as GitHub Workflow
    participant Publisher as JRubics/poetry-publish Action
    participant Poetry as Poetry Installer
    participant PyPI as PyPI Registry

    Workflow->>Publisher: Trigger publish step with new parameters
    Publisher-->>Poetry: Install dependencies (--without dev)
    Publisher->>Publisher: Set package directory (llama-index-server)
    Publisher->>PyPI: Publish package

Loading

Poem

I'm the rabbit on the run, with changes in my view,
Hopping through the config fields, making things shiny and new.
I left behind the old dev flags, ready to prove,
That a cleaner build process is a win for the groove!
With a skip and a bounce, my code is smooth! 🐇🌟

---

📜 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 2a4fb70 and 33eaeaf.

📒 Files selected for processing (1)

• .github/workflows/release_llama_index_server.yml (1 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.