Skip to content

Sync Future Version with main#35

Merged
juliolmuller merged 11 commits intonextfrom
main
Jan 12, 2026
Merged

Sync Future Version with main#35
juliolmuller merged 11 commits intonextfrom
main

Conversation

@juliolmuller
Copy link
Copy Markdown
Collaborator

@juliolmuller juliolmuller commented Jan 12, 2026

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions to newer versions across CI, license, and release workflows
    • Removed pull request trigger from CI workflow
    • Updated copyright years to 2026 across all license files
    • Migrated commit tooling from commitizen to commitlint-based configuration
    • Updated dependency management for commit automation

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

@juliolmuller juliolmuller requested a review from a team as a code owner January 12, 2026 12:56
@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Jan 12, 2026

⚠️ No Changeset found

Latest commit: d912a94

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link
Copy Markdown

vercel bot commented Jan 12, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
cpf-utils Ready Ready Preview, Comment Mar 23, 2026 7:57pm

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jan 12, 2026

📝 Walkthrough

Walkthrough

Migrated commit tooling from commitizen/cz-conventional-changelog to commitlint with workspace-scopes support, updated GitHub Actions to newer versions and removed PR-based CI triggers, and bumped copyright years to 2026 across root and package LICENSE files.

Changes

Cohort / File(s) Summary
Commit Tooling Migration
.commitlintrc, .czrc, commitlint.config.mjs, package.json
Removed .commitlintrc and .czrc configuration; added commitlint.config.mjs extending conventional and workspace-scopes presets. Updated package.json scripts (prepare: "husky", commit: "commit") and devDependencies, replacing commitizen/cz-conventional-changelog with @commitlint/config-workspace-scopes and @commitlint/prompt-cli.
GitHub Actions & Workflow Updates
.github/workflows/ci.yml, .github/workflows/license-update.yml, .github/workflows/pr-author-assign.yml, .github/workflows/release.yml
Updated checkout, setup-bun, and setup-node actions to newer versions; removed pull_request trigger from CI; upgraded auto-author-assign from v2.1.1 to v3.0.1; refactored combined type-check/lint run block into separate steps and added explicit parameters to changesets/action.
Copyright Year Updates
LICENSE, packages/br-utils/LICENSE, packages/cnpj-*/LICENSE, packages/cpf-*/LICENSE
Updated copyright year ranges across root and all package LICENSE files to include 2026 (e.g., 2020-2025 → 2020-2026).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

Possibly related PRs

Suggested labels

dependencies, refactoring

Poem

🐰 From commitizen hops to commitlint's neat rows,
Copyright blooms to twenty-twenty-six now shows,
Actions upgraded, PRs stopped for CI's grace,
Workspace scopes dance through this refactored place! ✨

🚥 Pre-merge checks | ✅ 3
✅ 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 'Sync Future Version with main' is clear and directly describes the primary intent of the pull request, which is to synchronize the next branch with the main branch.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings

📜 Recent review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e806df1 and d912a94.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (18)
  • .commitlintrc
  • .czrc
  • .github/workflows/ci.yml
  • .github/workflows/license-update.yml
  • .github/workflows/pr-author-assign.yml
  • .github/workflows/release.yml
  • LICENSE
  • commitlint.config.mjs
  • package.json
  • packages/br-utils/LICENSE
  • packages/cnpj-fmt/LICENSE
  • packages/cnpj-gen/LICENSE
  • packages/cnpj-utils/LICENSE
  • packages/cnpj-val/LICENSE
  • packages/cpf-fmt/LICENSE
  • packages/cpf-gen/LICENSE
  • packages/cpf-utils/LICENSE
  • packages/cpf-val/LICENSE
💤 Files with no reviewable changes (2)
  • .czrc
  • .commitlintrc
🔇 Additional comments (20)
packages/cpf-val/LICENSE (1)

3-3: LGTM! Copyright year updated appropriately.

The copyright year update to 2026 is correct and timely for the current year.

packages/cnpj-val/LICENSE (1)

3-3: LGTM! Copyright year updated appropriately.

The copyright year update to 2026 is correct and timely for the current year.

packages/cpf-utils/LICENSE (1)

3-3: LGTM! Copyright year updated appropriately.

The copyright year update to 2026 is correct and timely for the current year.

packages/cnpj-utils/LICENSE (1)

3-3: LGTM! Copyright year updated correctly.

The copyright year range has been appropriately updated to include 2026.

packages/br-utils/LICENSE (1)

3-3: LGTM! Copyright year updated correctly.

The copyright year range has been appropriately updated to include 2026.

packages/cpf-gen/LICENSE (1)

3-3: LGTM! Copyright year updated correctly.

The copyright year range has been appropriately updated to include 2026.

packages/cnpj-gen/LICENSE (1)

3-3: LGTM! Copyright year updated appropriately.

The copyright year range has been updated to include 2026, which is appropriate for the current year.

packages/cnpj-fmt/LICENSE (1)

3-3: LGTM! Copyright year updated appropriately.

The copyright year range has been updated to include 2026, consistent with the current year and other LICENSE files in this PR.

packages/cpf-fmt/LICENSE (1)

3-3: Verify the copyright holder change is intentional.

This line changes the copyright holder from "Lacus Solutions" (the organization) to "Julio L. Muller" (an individual), in addition to updating the year range to 2020-2026.

Copyright holder changes have legal implications. Please confirm this change is intentional and properly authorized, rather than an unintended modification during the merge from main to next.

LICENSE (1)

3-3: LGTM!

The copyright year update to 2026 is appropriate, and the year range format (2020-2026) correctly reflects the project's history.

.github/workflows/release.yml (3)

28-32: LGTM!

Action versions are consistently updated across this workflow, with proper SHA pinning for security.


39-40: LGTM!

Splitting type-check and lint into separate steps improves CI visibility and makes it easier to identify which check failed.


43-48: LGTM!

Explicit configuration for the changesets action improves maintainability. The commit message follows conventional commit format.

.github/workflows/license-update.yml (1)

18-18: LGTM!

The checkout action version is consistently updated to v6.0.1, matching other workflows in this PR.

Also applies to: 40-40

commitlint.config.mjs (1)

1-3: LGTM!

Clean migration to ESM-based commitlint configuration. Extending @commitlint/config-workspace-scopes properly enables workspace package names as valid commit scopes for this monorepo.

.github/workflows/ci.yml (2)

3-7: Verify the removal of pull_request trigger is intentional.

The workflow now only triggers on push and workflow_dispatch. While CI will still run when commits are pushed to PR branches, removing the explicit pull_request trigger means:

  • CI won't run on PR open/reopen/synchronize events from forks (fork pushes don't trigger push on the base repo)
  • Status checks may behave differently in branch protection rules

If this repository doesn't accept external contributions, this is likely fine.


23-24: LGTM!

Action versions are consistently updated across all jobs: actions/checkout@v6.0.1, oven-sh/setup-bun@v2.1.0, and actions/setup-node@v6.1.0. SHA pinning is properly used throughout.

Also applies to: 36-37, 48-49, 74-78

package.json (2)

85-86: LGTM!

The new commitlint dependencies are properly added to support workspace-scopes and the interactive commit prompt.


8-9: LGTM - Complete migration from commitizen to commitlint tooling.

  • prepare: Using husky directly is correct for Husky v9+
  • commit: The commit command is provided by @commitlint/prompt-cli which installs the binary

This completes the tooling migration mentioned in the PR objectives.

.github/workflows/pr-author-assign.yml (1)

16-16: The major version upgrade from v2.1.1 to v3.0.1 is safe with no breaking changes.

The v3.0.0 and v3.0.1 releases include internal improvements: Node.js runtime bumped to v24 and @actions/core dependency updated to 2.0.1. No user-facing breaking changes to the action's interface. SHA pinning provides security.


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

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

@juliolmuller
Copy link
Copy Markdown
Collaborator Author

@coderabbitai review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jan 12, 2026

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

@coderabbitai coderabbitai bot added dependencies Changes to the project dependencies. refactoring Non-functional improvements or changes. labels Jan 12, 2026
@juliolmuller juliolmuller merged commit b3a0537 into next Jan 12, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Changes to the project dependencies. refactoring Non-functional improvements or changes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant