fix: update go clean usage for newer Go versions

[sorccu]

Compatible with the old version (1.18) too.

Affected Components

• New Features
• Bug Fixing
• Types
• Tests
• Docs
• Other

Style

• Go code is formatted with go fmt

Notes for the Reviewer

Resolves #[issue-number]

New Dependency Submission

[coderabbitai]

Walkthrough

The Makefile's test target was updated by splitting the previous combined test cache and build artifact cleaning command into two separate commands: one for clearing the test cache globally and another for cleaning build artifacts across all packages. No changes were made to exported or public entities.

Changes

File	Change Summary
Makefile	Split go clean -testcache ./... into go clean -testcache and go clean ./... in test target.

Suggested reviewers

• maxigimenez

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

Makefile (1)

1-6: Declare targets as .PHONY to avoid name-shadowing

It’s common to add a .PHONY declaration so the targets don’t get skipped when files named test, demo, or fmt appear in the repo.

+ .PHONY: test demo fmt

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e583c54 and 65a7f73.

📒 Files selected for processing (1)

• Makefile (1 hunks)

🔇 Additional comments (1)

Makefile (1)

2-3: Split clean commands correctly for Go ≥1.20 — looks good

go clean -testcache (no patterns) is now the only form accepted by Go 1.20+, while go clean ./... preserves the full-package clean for 1.18. The two‐line split keeps both versions happy and has no side effects.

Nothing else to flag here. 👍