Skip to content

chore: update repository dependencies - #1803

Merged
Despire merged 6 commits into
masterfrom
chore/repo-dependencies
Jul 30, 2025
Merged

chore: update repository dependencies#1803
Despire merged 6 commits into
masterfrom
chore/repo-dependencies

Conversation

@Despire

@Despire Despire commented Jul 29, 2025

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Chores
    • Updated the CI pipeline to use a newer version of the linting tool.
    • Upgraded several Python package dependencies to their latest versions for improved stability and compatibility.
    • Updated container image tags in deployment configurations for consistency.

@Despire
Despire requested a review from m-brando July 29, 2025 11:30
@coderabbitai

coderabbitai Bot commented Jul 29, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

The changes update the GitHub Actions CI pipeline to use a newer version of the golangci-lint GitHub Action and upgrade several Python dependencies in the requirements.txt file to more recent versions. Additionally, numerous //nolint comments were added before specific exec.Command and net.Listen calls across multiple Go source files to suppress linter warnings. No public interfaces or logic were altered.

Changes

Cohort / File(s) Change Summary
CI Workflow Update
.github/workflows/CI-pipeline.yml
Updated golangci-lint GitHub Action from version 7 to version 8 and upgraded golangci-lint tool from v2.0.2 to v2.3.0.
Python Dependency Upgrades
requirements.txt
Upgraded multiple Python packages to newer versions, including certifi, charset-normalizer, click, Markdown, mkdocs plugins, Pygments, pymdown-extensions, requests, and urllib3.
Linter Suppression Comments for exec.Command
internal/command/cmd.go, internal/kubectl/kubectl.go, services/ansibler/server/utils/ansible.go, services/kube-eleven/server/domain/utils/kubeone/kubeone.go, services/terraformer/server/domain/utils/templates/templates.go, services/terraformer/server/domain/utils/templates/templates_test.go, services/terraformer/server/domain/utils/tofu/terraform.go
Added //nolint comments immediately before exec.Command calls to suppress linter warnings without changing logic or error handling.
Linter Suppression Comments for net.Listen
services/ansibler/server/adapters/inbound/grpc/adapter.go, services/autoscaler-adapter/main.go, services/claudie-operator/server/adapters/inbound/grpc/adapter.go, services/kube-eleven/server/adapters/inbound/grpc/adapter.go, services/kuber/server/adapters/inbound/grpc/adapter.go, services/manager/internal/service/grpc.go, services/terraformer/server/adapters/inbound/grpc/adapter.go
Added //nolint comments immediately before net.Listen calls to suppress linter warnings without changing logic or error handling.
Import Reordering and Linter Suppression
internal/kubectl/kubectl.go
Reordered imports to group standard library first, then external packages, and added //nolint comments before run and runWithOutput methods.
Image Tag Updates in Kustomizations
manifests/claudie/kustomization.yaml, manifests/testing-framework/kustomization.yaml
Updated container image tags for multiple services and testing framework to a new unified tag version.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

  • migrate to opentofu #1755: Updates image tags in the same manifests/claudie/kustomization.yaml file and includes related lint suppression changes, sharing a code-level connection through manifest updates and tooling.

Suggested reviewers

  • m-brando
  • bernardhalas

Poem

🐇
A hop and a skip, the linter’s anew,
Python packages freshened, all shiny and true.
With carrots for code and dependencies tight,
The CI hops forward, all systems alight!
Linter warnings silenced with gentle care,
The rabbit nods wisely, no errors to bear.
Another quick patch, reviewed in a flash—
The rabbit approves, then off in a dash!


📜 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 7306621 and c2181b8.

📒 Files selected for processing (2)
  • manifests/claudie/kustomization.yaml (1 hunks)
  • manifests/testing-framework/kustomization.yaml (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • manifests/testing-framework/kustomization.yaml
  • manifests/claudie/kustomization.yaml
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/repo-dependencies

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
🪧 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 generate unit tests to generate unit tests for 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 coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 42941c8 and 6fd4ef2.

📒 Files selected for processing (2)
  • .github/workflows/CI-pipeline.yml (1 hunks)
  • requirements.txt (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: Despire
PR: berops/claudie#1749
File: manifests/testing-framework/test-sets/test-set5/1.yaml:65-65
Timestamp: 2025-06-10T14:27:44.312Z
Learning: When Despire declines to address consistency issues like version string prefixes in a focused PR (e.g., kubeone updates), they prefer to handle such standardization in separate issues rather than expanding the scope of the current PR.
.github/workflows/CI-pipeline.yml (2)

Learnt from: Despire
PR: #1795
File: services/testing-framework/Dockerfile:1-1
Timestamp: 2025-07-29T08:19:28.042Z
Learning: Always verify the current availability of Docker images and software versions before flagging them as non-existent, as release schedules can advance beyond expectations. Go has progressed beyond 1.22.x to 1.24.5 as of July 2025.

Learnt from: Despire
PR: #1795
File: services/terraformer/Dockerfile:1-1
Timestamp: 2025-07-29T08:19:23.486Z
Learning: Before claiming that a Docker image tag doesn't exist, always verify its existence by checking Docker Hub or the official registry. golang:1.24.5 is a valid tag that exists on Docker Hub despite not appearing in the official Go GitHub releases, as Docker images may have patch versions that differ from the official Go release numbering.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: gotest
  • GitHub Check: Run golangci-lint
🔇 Additional comments (2)
requirements.txt (1)

1-3: Dependency pins verified—no breaking changes detected

  • All new pins in requirements.txt (including certifi 2025.7.14, charset-normalizer 3.4.2, click 8.2.1, pyyaml_env_tag 1.1, requests 2.32.4, urllib3 2.5.0, etc.) exist on PyPI and install successfully.
  • No internal transitive‐dependency conflicts were raised when installing these requirements in isolation:
    • The major jump from pyyaml_env_tag 0.1 → 1.1 did not break mkdocs-material* or mkdocs-include-markdown-plugin.
    • requests==2.32.4 remains compatible with its <3 constraint on urllib3 while using urllib3==2.5.0.
  • The only pip-check warning (semgrep 1.128.1 requires click~=8.1.8) stems from a globally installed Semgrep and is not part of this project’s requirements—using a clean virtual environment will eliminate it.

No further action required before merging.

.github/workflows/CI-pipeline.yml (1)

104-110: Verified golangci-lint-action@v8 and version input
Both checks passed:

  • The golangci/golangci-lint-action@v8 tag exists.
  • The version input is still defined in v8’s action.yml.

No changes required.

Comment thread requirements.txt Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9e730af and b07da11.

📒 Files selected for processing (14)
  • internal/command/cmd.go (1 hunks)
  • internal/kubectl/kubectl.go (3 hunks)
  • services/ansibler/server/adapters/inbound/grpc/adapter.go (1 hunks)
  • services/ansibler/server/utils/ansible.go (1 hunks)
  • services/autoscaler-adapter/main.go (1 hunks)
  • services/claudie-operator/server/adapters/inbound/grpc/adapter.go (1 hunks)
  • services/kube-eleven/server/adapters/inbound/grpc/adapter.go (1 hunks)
  • services/kube-eleven/server/domain/utils/kubeone/kubeone.go (2 hunks)
  • services/kuber/server/adapters/inbound/grpc/adapter.go (1 hunks)
  • services/manager/internal/service/grpc.go (1 hunks)
  • services/terraformer/server/adapters/inbound/grpc/adapter.go (1 hunks)
  • services/terraformer/server/domain/utils/templates/templates.go (5 hunks)
  • services/terraformer/server/domain/utils/templates/templates_test.go (1 hunks)
  • services/terraformer/server/domain/utils/tofu/terraform.go (6 hunks)
✅ Files skipped from review due to trivial changes (13)
  • services/kube-eleven/server/adapters/inbound/grpc/adapter.go
  • services/kube-eleven/server/domain/utils/kubeone/kubeone.go
  • services/kuber/server/adapters/inbound/grpc/adapter.go
  • services/terraformer/server/adapters/inbound/grpc/adapter.go
  • services/ansibler/server/utils/ansible.go
  • services/ansibler/server/adapters/inbound/grpc/adapter.go
  • services/claudie-operator/server/adapters/inbound/grpc/adapter.go
  • services/terraformer/server/domain/utils/templates/templates_test.go
  • services/terraformer/server/domain/utils/tofu/terraform.go
  • services/manager/internal/service/grpc.go
  • services/terraformer/server/domain/utils/templates/templates.go
  • internal/command/cmd.go
  • services/autoscaler-adapter/main.go
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: Despire
PR: berops/claudie#1795
File: services/testing-framework/Dockerfile:1-1
Timestamp: 2025-07-29T08:19:28.042Z
Learning: Always verify the current availability of Docker images and software versions before flagging them as non-existent, as release schedules can advance beyond expectations. Go has progressed beyond 1.22.x to 1.24.5 as of July 2025.
Learnt from: Despire
PR: berops/claudie#1749
File: manifests/testing-framework/test-sets/test-set5/1.yaml:65-65
Timestamp: 2025-06-10T14:27:44.312Z
Learning: When Despire declines to address consistency issues like version string prefixes in a focused PR (e.g., kubeone updates), they prefer to handle such standardization in separate issues rather than expanding the scope of the current PR.
🔇 Additional comments (2)
internal/kubectl/kubectl.go (2)

11-14: LGTM: Import grouping follows Go conventions.

The reordering of imports to group standard library packages first, followed by external packages, aligns with Go best practices and improves code readability.


257-257: Ensure safe use of //nolint on exec.Command

The blanket //nolint at internal/kubectl/kubectl.go:257 silences all linter warnings on:

cmd := exec.Command("bash", "-c", strings.Join(append([]string{command}, options...), " "))

Suppressing linter errors here could mask a command-injection risk if command or options ever originate from untrusted data. Please:

  • Confirm that every call site of Kubectl.run only passes hard-coded or fully validated strings.
  • Prefer invoking the executable directly instead of via shell, for example:
  • cmd := exec.Command("bash", "-c", strings.Join(append([]string{command}, options...), " "))
  • cmd := exec.Command(command, options...)
- If you still need to suppress specific warnings, scope the directive to the exact linter rule (e.g., `//nolint:gosec`), not all linters.

Review internal/kubectl/kubectl.go and every `Kubectl.run(…)` invocation to ensure no untrusted input can slip through.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

Comment thread internal/kubectl/kubectl.go
@Despire
Despire added this pull request to the merge queue Jul 30, 2025
Merged via the queue into master with commit a7612fa Jul 30, 2025
1 check passed
@Despire
Despire deleted the chore/repo-dependencies branch July 30, 2025 07:07
@coderabbitai coderabbitai Bot mentioned this pull request Dec 2, 2025
@coderabbitai coderabbitai Bot mentioned this pull request Feb 4, 2026
This was referenced May 29, 2026
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