Cascade dependencies update

[juliolmuller]

Summary by CodeRabbit

• Chores
  • Updated internal package dependencies to patch versions across cnpj-utils and cpf-utils packages
  • Tightened dependency version constraints to restrict compatibility with major version 2.0 and above
  • Updated documentation to reflect dependency version changes

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Dependencies are updated across cnpj-utils and cpf-utils packages with version bumps applied consistently to pyproject.toml, requirements.txt, and CHANGELOG.md files. Dependency constraints are tightened by adding upper bounds (<2.0.0) while minimum versions are selectively incremented.

Changes

Cohort / File(s)	Summary
CNPJ Utils Changelog packages/cnpj-utils/CHANGELOG.md	Added v1.0.2 entry documenting patch updates to cnpj-gen and cnpj-val dependencies (both 1.0.1 → 1.0.2)
CPF Utils Changelog packages/cpf-utils/CHANGELOG.md	Added v1.0.1 entry documenting patch updates to cpf-gen and cpf-val dependencies (both 1.0.0 → 1.0.1)
CNPJ Utils Dependencies packages/cnpj-utils/pyproject.toml	Tightened constraints for cnpj-gen and cnpj-val to >=1.0.2,<2.0.0; cnpj-fmt now constrained to >=1.0.0,<2.0.0
CPF Utils Dependencies packages/cpf-utils/pyproject.toml	Updated cpf-gen and cpf-val to >=1.0.1,<2.0.0; cpf-fmt now constrained to >=1.0.0,<2.0.0
Root Requirements requirements.txt	Bumped cnpj-gen and cnpj-val to 1.0.2; bumped cpf-gen and cpf-val to 1.0.1

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

enhancement

Poem

🐰 Hops through the versions with glee,
Dependencies dance in harmony,
Upper bounds set, minimums rise,
A tidy patch before our eyes,
Clean constraints, no breaking surprise!

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 accurately describes the main change—updating dependencies across multiple packages in a coordinated manner.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch refactor/update-cd-to-dv

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5359ad1 and 73ef6f1.

📒 Files selected for processing (5)

• packages/cnpj-utils/CHANGELOG.md
• packages/cnpj-utils/pyproject.toml
• packages/cpf-utils/CHANGELOG.md
• packages/cpf-utils/pyproject.toml
• requirements.txt

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: juliolmuller
Repo: LacusSolutions/br-utils-py PR: 42
File: packages/cpf-utils/src/cpf_utils/__init__.py:40-40
Timestamp: 2025-12-25T13:28:29.082Z
Learning: In the br-utils-py repository, the `__version__` variable in package `__init__.py` files is dynamically updated during the build and release workflow, so it should remain as "0.0.0" in the source code.

🔇 Additional comments (5)

packages/cnpj-utils/CHANGELOG.md (1)

3-10: LGTM! Changelog entry accurately reflects dependency updates.

The 1.0.2 changelog entry correctly documents the patch-level dependency bumps for cnpj-gen and cnpj-val, consistent with the changes in pyproject.toml.

packages/cpf-utils/CHANGELOG.md (1)

3-10: LGTM! Changelog entry accurately reflects dependency updates.

The 1.0.1 changelog entry correctly documents the patch-level dependency bumps for cpf-gen and cpf-val, consistent with the changes in pyproject.toml.

packages/cnpj-utils/pyproject.toml (1)

42-44: LGTM! Dependency constraints appropriately tightened.

The changes accomplish two improvements:

1. Adding the <2.0.0 upper bound follows semantic versioning best practices and prevents automatic upgrades to potentially breaking major versions.
2. Bumping minimum versions for cnpj-gen and cnpj-val to 1.0.2 ensures users get the latest patches.

The constraint strategy balances flexibility (allowing patch/minor updates) with stability (preventing major version breaks).

packages/cpf-utils/pyproject.toml (1)

42-44: LGTM! Dependency constraints appropriately tightened.

The changes mirror the approach used in cnpj-utils:

1. Adding the <2.0.0 upper bound protects against breaking changes in major version updates.
2. Bumping minimum versions for cpf-gen and cpf-val to 1.0.1 ensures users receive the latest patches.

This consistent versioning strategy across both utils packages maintains good dependency hygiene.

requirements.txt (1)

3-4: All specified dependency versions are available on PyPI.

Verification confirms that cnpj-gen 1.0.2, cnpj-val 1.0.2, cpf-gen 1.0.1, and cpf-val 1.0.1 all exist and are published. The build will not break due to missing package versions.

---

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.}