Skip to content
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.

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

feat(build): drop Go 1.21 support #82

Merged
merged 1 commit into from
Jan 12, 2025
Merged

feat(build): drop Go 1.21 support #82

merged 1 commit into from
Jan 12, 2025

Conversation

karasz
Copy link
Collaborator

@karasz karasz commented Jan 12, 2025

Summary by CodeRabbit

Release Notes

  • Chores

    • Upgraded Go version from 1.21 to 1.22 across project modules
    • Updated GitHub Actions workflow to test Go versions 1.22 and 1.23
    • Modified linter configurations to improve code quality checks
  • Build

    • Updated build and dependency management configurations to support Go 1.22

@karasz karasz requested a review from amery January 12, 2025 17:55
Copy link

coderabbitai bot commented Jan 12, 2025

Warning

Rate limit exceeded

@karasz has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 53 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between cb27236 and ecf8fe7.

📒 Files selected for processing (11)
  • .github/workflows/build.yml (1 hunks)
  • .golangci.yml (1 hunks)
  • Makefile (1 hunks)
  • go.mod (1 hunks)
  • handlers/cblog/go.mod (1 hunks)
  • handlers/discard/go.mod (1 hunks)
  • handlers/filter/go.mod (1 hunks)
  • handlers/logrus/go.mod (1 hunks)
  • handlers/zap/go.mod (1 hunks)
  • handlers/zerolog/go.mod (1 hunks)
  • renovate.json (1 hunks)

Walkthrough

This pull request primarily focuses on upgrading the project's Go version from 1.21 to 1.22. The changes span multiple configuration files, including GitHub Actions workflow, linting configuration, Makefile, go.mod files across different modules, and the Renovate configuration. The upgrade involves updating Go version specifications, adjusting CI/CD matrix, modifying linter settings, and ensuring compatibility with the new Go version.

Changes

File Change Summary
.github/workflows/build.yml Removed Go 1.21 from CI matrix, now testing only Go 1.22 and 1.23
.golangci.yml Disabled exportloopref linter, enabled copyloopvar linter, added new Revive linter rules
Makefile Updated tool versions for GOLANGCI_LINT and REVIVE to use Go 1.22
go.mod (root and handlers) Updated Go version from 1.21 to 1.22 across multiple modules
renovate.json Updated allowed Go version from 1.21 to 1.22

Possibly related PRs

Suggested labels

enhancement

Poem

🐰 Hop, skip, and a version jump!
From 1.21 to 1.22 we leap,
Linters dance, workflows reset,
A rabbit's code upgrade, so neat!
Go forward, progress complete! 🚀


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

.github/workflows/build.yml Show resolved Hide resolved
.golangci.yml Show resolved Hide resolved
Makefile Show resolved Hide resolved
Makefile Show resolved Hide resolved
go.mod Show resolved Hide resolved
handlers/filter/go.mod Show resolved Hide resolved
handlers/logrus/go.mod Show resolved Hide resolved
handlers/zap/go.mod Show resolved Hide resolved
handlers/zerolog/go.mod Show resolved Hide resolved
renovate.json Show resolved Hide resolved
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
renovate.json (1)

9-9: Consider allowing both Go 1.22 and 1.23

The current configuration only allows Go 1.22, but the build matrix in .github/workflows/build.yml includes both 1.22 and 1.23. Consider using "allowedVersions": ">=1.22 <1.24" to match the build matrix.

-      "allowedVersions": "1.22"
+      "allowedVersions": ">=1.22 <1.24"
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9f51e1a and 4ce5566.

📒 Files selected for processing (11)
  • .github/workflows/build.yml (1 hunks)
  • .golangci.yml (1 hunks)
  • Makefile (1 hunks)
  • go.mod (1 hunks)
  • handlers/cblog/go.mod (1 hunks)
  • handlers/discard/go.mod (1 hunks)
  • handlers/filter/go.mod (1 hunks)
  • handlers/logrus/go.mod (1 hunks)
  • handlers/zap/go.mod (1 hunks)
  • handlers/zerolog/go.mod (1 hunks)
  • renovate.json (1 hunks)
✅ Files skipped from review due to trivial changes (7)
  • handlers/discard/go.mod
  • handlers/logrus/go.mod
  • handlers/cblog/go.mod
  • handlers/filter/go.mod
  • handlers/zap/go.mod
  • handlers/zerolog/go.mod
  • go.mod
🔇 Additional comments (3)
.github/workflows/build.yml (1)

15-15: LGTM! Matrix configuration aligns with Go version upgrade

The build matrix correctly removes Go 1.21 while maintaining Go 1.22 and 1.23 for forward compatibility.

.golangci.yml (1)

45-45: LGTM! Appropriate linter updates for Go 1.22

The replacement of exportloopref with copyloopvar is correct as exportloopref is deprecated in Go 1.22. The new linter provides the same functionality with improved compatibility.

Makefile (1)

18-19: LGTM! Tool versions are compatible with Go 1.22

The updated versions for golangci-lint (v1.63.4) and revive (v1.4) are compatible with Go 1.22.

.golangci.yml Outdated Show resolved Hide resolved
@karasz karasz requested a review from amery January 12, 2025 19:31
Copy link
Collaborator

@amery amery left a comment

Choose a reason for hiding this comment

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

One commit please, not two

Signed-off-by: Nagy Károly Gábriel <k@jpi.io>
Copy link
Collaborator

@amery amery left a comment

Choose a reason for hiding this comment

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

Looks good

@amery amery merged commit 77db903 into main Jan 12, 2025
9 checks passed
@karasz karasz deleted the pr-karasz-go122 branch January 13, 2025 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants