Release 3.5.1

[GaetanLepage]

Release 3.5.1 of nixpkgs-review

Summary by CodeRabbit

• Chores
  • Bumped application version to 3.5.1.
  • No user-facing changes; existing features and behavior remain unchanged.
  • No configuration updates required; compatibility and integrations unaffected.
  • Safe maintenance release with no impact on performance or workflows.
  • No API or interface adjustments; upgrades should be seamless.
  • Recommended to align with the latest release tag and ensure version consistency across environments.

[coderabbitai]

Walkthrough

Version updated in pyproject.toml from 3.5.0 to 3.5.1. No other changes detected.

Changes

Cohort / File(s)	Summary
Release metadata pyproject.toml	Bump project version: 3.5.0 → 3.5.1; no functional or structural code changes

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Release 3.5.0 #557 — Similar version bump in pyproject.toml (3.4.0→3.5.0), indicating related release metadata updates.

Poem

A hop and a skip, the numbers climb,
From dot-oh to dot-one—right on time.
I thump my paw: “Release is done!”
Carrots queued for 3.5.1. 🥕
Small step, soft breeze, new build fun!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Release 3.5.1" is concise and directly reflects the primary change in the changeset (a version bump to 3.5.1 in pyproject.toml) and aligns with the PR objective of publishing release 3.5.1, making it clear for teammates scanning history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-3.5.1

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

pyproject.toml (1)

8-8: Optional: switch to setuptools-scm for auto-versioning

To avoid manual bumps each release, consider deriving the version from Git tags.

If desired, change Line 8 and add config:

- version = "3.5.1"
+ dynamic = ["version"]

Then add (outside the shown range, near other tool configs):

[tool.setuptools_scm]
version_scheme = "post-release"
local_scheme = "no-local-version"

And ensure build requires a recent setuptools_scm:

[build-system]
requires = ["setuptools>=64", "setuptools-scm>=8"]

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a6ec1b3 and 7cf1029.

📒 Files selected for processing (1)

• pyproject.toml (1 hunks)

🔇 Additional comments (1)

pyproject.toml (1)

8-8: LGTM — version bumped to 3.5.1

Verified: no occurrences of "3.5.0" or "version" found; only match is pyproject.toml:8 — version = "3.5.1". Confirm Git tag and release notes updated to 3.5.1.