Add jumpstarter-all to package building

[mangelajo]

Summary by CodeRabbit

• Chores
  • Added a new workspace source entry named "jumpstarter-all" to the configuration settings.

[coderabbitai]

Walkthrough

A new source workspace entry named jumpstarter-all was added to the [tool.uv.sources] section in the pyproject.toml file. This entry is configured with workspace = true, aligning it with other existing workspace source entries in the configuration. No other changes or updates were made to the file.

Changes

File	Change Summary
pyproject.toml	Added jumpstarter-all = { workspace = true } to [tool.uv.sources] section.

Poem

A hop and a skip, a new source appears,
In pyproject’s garden, it now volunteers.
jumpstarter-all joins the workspace crew,
Ready for tasks, with much to do!
🐇✨

---

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[netlify]

✅ Deploy Preview for jumpstarter-docs ready!

Name	Link
🔨 Latest commit	3cad994
🔍 Latest deploy log	https://app.netlify.com/sites/jumpstarter-docs/deploys/6811df94e230260008f0e482
😎 Deploy Preview	https://deploy-preview-433--jumpstarter-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

pyproject.toml (1)

5-9: Optional: Keep source entries alphabetically ordered.

For improved readability and maintainability, consider moving jumpstarter-all before jumpstarter-cli:

-jumpstarter-cli = { workspace = true }
-jumpstarter-all = { workspace = true }
+jumpstarter-all    = { workspace = true }
+jumpstarter-cli    = { workspace = true }

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1a25ddd and 3cad994.

📒 Files selected for processing (1)

• pyproject.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (8)

• GitHub Check: pytest-matrix (3.12)
• GitHub Check: pytest-matrix (3.11)
• GitHub Check: pytest-matrix (3.13)
• GitHub Check: e2e
• GitHub Check: build-and-push-image (jumpstarter-dev/jumpstarter-devspace .devfile/Containerfile.client)
• GitHub Check: build-and-push-image (jumpstarter-dev/jumpstarter-utils Dockerfile.utils)
• GitHub Check: build-and-push-image (jumpstarter-dev/jumpstarter-dev .devfile/Containerfile)
• GitHub Check: build-and-push-image (jumpstarter-dev/jumpstarter Dockerfile)

🔇 Additional comments (1)

pyproject.toml (1)

7-7:

Details

✅ Verification successful

Approve addition of jumpstarter-all to workspace sources.

The new entry jumpstarter-all = { workspace = true } follows the existing pattern and ensures this package is included in the build. Please verify that a corresponding packages/jumpstarter-all directory exists and contains the necessary metadata (e.g., its own pyproject.toml).

Run this to confirm the folder’s presence:

---

🏁 Script executed:

#!/bin/bash
# Verify that "packages/jumpstarter-all" exists
fd --type d "^packages/jumpstarter-all$"

Length of output: 42

---

🏁 Script executed:

#!/bin/bash
# Search for any directory named "jumpstarter-all" anywhere in the repo
fd --type d 'jumpstarter-all'

Length of output: 55

---

🏁 Script executed:

#!/bin/bash
# Verify that "packages/jumpstarter-all/pyproject.toml" exists
fd --type f 'pyproject.toml' packages/jumpstarter-all

Length of output: 93

---

Approve addition of jumpstarter-all to workspace sources

The packages/jumpstarter-all directory and its pyproject.toml have been verified to exist. No further action is required.

• packages/jumpstarter-all/pyproject.toml

[mangelajo]

Ignore it... apparently -all is being built hmmm, but not locally in my devel env for some reason.