Skip to content

build(deps): update pyyaml requirement from >=6.0.0 to >=6.0.3 #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

build(deps): update pyyaml requirement from >=6.0.0 to >=6.0.3 #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ pydantic = "^2.10.0"
pydantic-settings = "^2.6.0"
httpx = "^0.28.0"
structlog = "^25.0.0"
pyyaml = ">=6.0.0"
pyyaml = ">=6.0.3"

@coderabbitai coderabbitai Bot Apr 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

🧩 Analysis chain

🌐 Web query:

What is the latest PyYAML version, and are there any documented breaking changes between PyYAML 6.x and 7.x (or planned next major) that would affect using an unbounded constraint like ">=6.0.3" in Poetry?

💡 Result:

The latest PyYAML version is 6.0.3, released on 2025-09-25. There are no released versions of PyYAML 7.x as of 2026-04-13. The main branch CHANGES file mentions a placeholder "7.0.0.dev0 (TBD)" with no specific changes listed. All 6.x releases (6.0 through 6.0.3) consist of bug fixes, Python version support updates (e.g., Python 3.13, 3.14), and minor improvements, with no documented breaking changes relative to 6.0. The jump from 5.x to 6.0 included dropping Python 2.7 support and requiring a Loader argument for yaml.load, but within 6.x, changes are backwards-compatible. No evidence of planned breaking changes for a future 7.x that would affect an unbounded ">=6.0.3" constraint in Poetry; it would resolve to the latest 6.0.3 safely. A project exists for "PyYAML 6.1 release planning" updated May 2025, but no release yet and likely minor.

Citations:

Consider bounding PyYAML to major 6 for consistency with dependency policy.

At Line 17, pyyaml = ">=6.0.3" uses an unbounded constraint while most other dependencies use caret constraints (e.g., ^0.x, ^2.x). Although PyYAML 7.x does not currently exist and has no documented breaking changes planned, aligning with the caret pattern (^6.0.3) would be safer and more consistent with the project's dependency strategy.

Proposed change 
-pyyaml = ">=6.0.3"
+pyyaml = "^6.0.3"

(Equivalent explicit form: >=6.0.3,<7.0.0)

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
pyyaml = ">=6.0.3"
pyyaml = "^6.0.3"
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@pyproject.toml` at line 17, Update the PyYAML dependency declaration in
pyproject.toml from the unbounded form `pyyaml = ">=6.0.3"` to a caret-bounded
form to pin the major version (for example `pyyaml = "^6.0.3"` or the equivalent
explicit range `pyyaml = ">=6.0.3,<7.0.0"`); modify the `pyyaml` dependency line
so it follows the project's caret-style constraints.

prometheus-client = "^0.24.1"

[tool.poetry.group.dev.dependencies]
Expand Down
Loading