add skip count license header lines

[kmrmt]

Description

SSIA
Merge only this or #2851

Related Issue

Versions

• Vald Version: v1.7.16
• Go Version: v1.23.6
• Rust Version: v1.83.0
• Docker Version: v27.4.0
• Kubernetes Version: v1.32.0
• Helm Version: v3.16.3
• NGT Version: v2.3.5
• Faiss Version: v1.9.0

Checklist

• I have read the CONTRIBUTING document and completed our CLA agreement.
• I have checked open Pull Requests for the similar feature or fixes?

Special notes for your reviewer

Summary by CodeRabbit

• Chores
  • Streamlined the internal process for managing dependency updates, resulting in a more efficient build workflow.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request modifies the go/deps target in the Makefile.d/dependencies.mk file. The dependency on update/go has been removed, and the target now executes its commands directly—from reading the $(ROOTDIR)/hack/go.mod.default file to filtering, sorting, and updating the Go version. The go/example/deps target remains unchanged.

Changes

File(s)	Change Summary
Makefile.d/dependencies.mk	Removed the dependency on update/go from the go/deps target; commands for reading, filtering, sorting, and updating Go module data now execute directly.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant GDeps as go/deps Target
    participant Shell as Shell Commands

    Dev->>GDeps: Execute go/deps target
    GDeps->>Shell: Read $(ROOTDIR)/hack/go.mod.default
    Shell-->>GDeps: Return file content
    GDeps->>Shell: Filter and sort module lines
    Shell-->>GDeps: Return processed data
    GDeps->>Shell: Update Go version in file
    Shell-->>GDeps: Confirm update
    GDeps->>Dev: Return completion status

Loading

Possibly related PRs

• Remove update/go from go/deps cmd #2848: Involves removal of the update/go dependency from the go/deps target in the same Makefile, which directly relates to these changes.

Suggested labels

type/refactoring, area/makefile

Suggested reviewers

• kpango
• vankichi

---

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

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

[vdaas-ci]

[CHATOPS:HELP] ChatOps commands.

• 🙆‍♀️ /approve - approve
• 🍱 /format - format codes and add licenses
• ✅ /gen-test - generate test codes
• 🏷️ /label - add labels
• 🔚 2️⃣ 🔚 /label actions/e2e-deploy - run E2E deploy & integration test

[cloudflare-workers-and-pages]

Deploying vald with    Cloudflare Pages

Latest commit:	9090f6e
Status:	✅  Deploy successful!
Preview URL:	https://65fa48d2.vald.pages.dev
Branch Preview URL:	https://bugfix-charts-yaml-format.vald.pages.dev

View logs

[coderabbitai]

Actionable comments posted: 1

🔭 Outside diff range comments (1)

Makefile.d/dependencies.mk (1)

75-75: 🛠️ Refactor suggestion

Replace discouraged command and avoid error suppression.

The command go get -u all is discouraged in Go modules as it can lead to unexpected version upgrades. Additionally, suppressing errors with 2>/dev/null can hide important issues.

Apply this diff to use the recommended approach:

-	go get -u all 2>/dev/null || true
+	# Update dependencies to latest minor/patch versions
+	go get -u=patch ./... || echo "Warning: Some patches could not be applied"

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2c81fe3 and 9090f6e.

⛔ Files ignored due to path filters (1)

• hack/license/gen/main.go is excluded by !**/gen/**

📒 Files selected for processing (1)

• Makefile.d/dependencies.mk (1 hunks)