chore: clean up repo

[aljo242]

Summary by CodeRabbit

• Chores
  • Updated the version of the linter tool used in development.
  • Removed formatting-related commands from the development workflow.
  • Minor adjustments to command output during build tasks (no impact on end-user experience).

[coderabbitai]

Walkthrough

The Makefile was updated by suppressing the command echo in the legacydump target, removing the format target and its formatting commands, and updating the golangci_version variable from v2.0.2 to v2.1.6.

Changes

File	Change Summary
Makefile	Suppressed echo in legacydump, removed format target, updated linter version.

Poem

In the warren where Makefiles hop,
Echoes now quietly drop.
Formatting tasks have hopped away,
A newer linter comes to play.
With silent steps and tidy code,
The rabbit bounds down a streamlined road!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4027b8d and 364293d.

📒 Files selected for processing (1)

• Makefile (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Test
• GitHub Check: Benchmarks
• GitHub Check: Analyze (go)

🔇 Additional comments (2)

Makefile (2)

28-28: Suppress command echo for consistency
Adding @ before the cd cmd/legacydump ... command keeps the Make output clean and matches the style used in other targets.

---

37-37: Verify the linter version bump
The golangci_version was updated from v2.0.2 to v2.1.6. Please confirm that this version is available, compatible with your CI setup, and that any documentation or scripts referencing the old version are updated accordingly.

---

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

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

[aljo242]

@Mergifyio backport release/v1.3.x

[aljo242]

@Mergifyio backport release/v1.2.x

[mergify]

backport release/v1.3.x

✅ Backports have been created

• #1101 chore: clean up repo (backport #1100) has been created for branch release/v1.3.x but encountered conflicts

[mergify]

backport release/v1.2.x

✅ Backports have been created

• #1102 chore: clean up repo (backport #1100) has been created for branch release/v1.2.x