Centralize glam and ordered-float versions

[leynos]

Summary

• share glam and ordered-float versions across the workspace via [workspace.dependencies]

Testing

• make fmt
• make markdownlint
• make lint
• make test

---

https://chatgpt.com/codex/tasks/task_e_685b2e36c26883228ff955f0b3c05977

Summary by Sourcery

Centralize the version requirements for glam and ordered-float in the workspace manifest and update crate references to use workspace dependencies

Enhancements:

• Centralize glam and ordered-float versions into the workspace dependencies section

Build:

• Update root Cargo.toml to reference glam and ordered-float via workspace dependencies

[sourcery-ai]

Reviewer's Guide

This PR centralizes the version specifications for glam and ordered-float by declaring them once under [workspace.dependencies] in Cargo.toml and updates all individual references to use the workspace-defined versions (workspace = true) instead of hardcoded version strings.

Class diagram for Cargo.toml dependency management changes

classDiagram
    class Workspace {
        +glam: 0.24
        +ordered-float: 2
    }
    class MainCrate {
        +glam: workspace = true
        +ordered-float: workspace = true
    }
    Workspace <|-- MainCrate: uses dependencies from

Loading

File-Level Changes

Change	Details	Files
Introduce a workspace-wide dependency declaration	Add a [workspace.dependencies] section Define glam = "0.24" Define ordered-float = "2"	Cargo.toml
Switch individual crates to reference workspace dependencies	Change glam dependency to use workspace = true Change ordered-float in dev-dependencies to use workspace = true	Cargo.toml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Updated dependency management to use workspace-level versioning for improved consistency across the project. No changes to application functionality.

Walkthrough

The dependency management in the Cargo.toml file was updated to use workspace-level inheritance for the glam and ordered-float crates. Explicit versions were removed from individual dependency declarations and centralised under a new [workspace.dependencies] section.

Changes

File	Change Summary
Cargo.toml	Updated glam and ordered-float dependencies to use { workspace = true }; added [workspace.dependencies] section for centralised version management.

Poem

In the warren of code, dependencies align,
Now centralised neatly, all by design.
No more version clutter, the workspace is clear,
Rabbits rejoice, for order is here!
🥕✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 37844d2 and 94a8167.

📒 Files selected for processing (1)

• Cargo.toml (2 hunks)

🔇 Additional comments (3)

Cargo.toml (3)

31-33: [workspace.dependencies] correctly added – ensure minimum toolchain ≥ 1.64

workspace.dependencies became stable in Rust 1.64. If CI still targets an older toolchain, builds will fail. Otherwise this change is spot-on and removes version duplication.

---

41-41: Dev dependency tied to workspace – good consistency

Aligning ordered-float with the workspace table prevents accidental drift between test and production code. No issues spotted.

---

11-11: glam successfully centralised – verify that no local versions remain

The switch to { workspace = true } is correct and keeps glam in-sync across crates. Double-check that every other Cargo.toml in the workspace has dropped its own glam version stanza to avoid duplicate feature resolution or mixed minor versions.

#!/bin/bash
# Find any lingering explicit glam version declarations
rg --no-heading --line-number $'glam[[:space:]]*=.*"[0-9]' --glob 'Cargo.toml'

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment
• Commit Unit Tests in branch codex/centralize-dependencies-for-ordered-float-and-glam

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 auto-generate unit tests to generate unit tests for 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.

[leynos]

@sourcery-ai review

[leynos]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[sourcery-ai]

Hey @leynos - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}