ci: split go and devenv tests

[xenOs76]

Summary by CodeRabbit

• Chores
  • Updated CI/CD workflow configuration to improve testing and release processes with enhanced validation sequences and additional compatibility checks.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Warning

Rate limit exceeded

@xenOs76 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 5 minutes and 15 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 ef1571a and 37fc670.

📒 Files selected for processing (2)

• .github/workflows/codeChecks.yml (4 hunks)
• .goreleaser.yaml (1 hunks)

Walkthrough

The .github/workflows/codeChecks.yml workflow was restructured to replace the single code_checks job with three sequential jobs: go_tests (with matrix configuration for multiple Go versions), devenv_tests (dependent on go_tests), and goreleaser_test (dependent on devenv_tests). This establishes a new job dependency chain for build, test, and release tooling validation.

Changes

Cohort / File(s)	Change Summary
GitHub Actions Workflow Restructuring .github/workflows/codeChecks.yml	Replaced code_checks job with three new sequential jobs: go_tests (includes Go version matrix, builds, tests, vulnerability checks), devenv_tests (runs devenv-based build/test suite), and goreleaser_test (sets up QEMU/Go, runs GoReleaser, refreshes Go Report Card). Introduces job dependencies: go_tests → devenv_tests → goreleaser_test.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify the new job sequencing and dependency chain are correct (go_tests → devenv_tests → goreleaser_test)
• Confirm Go version matrix configuration matches project requirements
• Validate step names and action references (QEMU setup, GoReleaser, Go Report Card)
• Ensure devenv integration steps are properly configured

Possibly related PRs

• ci: add devenv test to code checks #16: Modifies CI workflows to extend devenv-based tests and adjust code checks/release job sequencing in .github/workflows.

Poem

🐰 Workflows now flow with grace and care,
Go tests lead, then devenv checks prepare,
GoReleaser follows the way,
Each step depends on the one before, hooray! 🚀

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'ci: split go and devenv tests' directly and accurately describes the main change: splitting CI workflows into separate Go and devenv test jobs.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.github/workflows/codeChecks.yml (1)

19-19: Consider removing the max-parallel constraint.

Setting max-parallel: 1 forces the matrix jobs to run sequentially, which defeats the purpose of using a matrix strategy and significantly increases CI time. Unless there's a specific resource constraint or rate-limiting concern, removing this line would allow both Go versions to be tested in parallel.

🔎 Apply this diff to enable parallel execution:

    strategy:
-     max-parallel: 1
      matrix:
        go-version: ['1.24', '1.25']

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5160935 and ef1571a.

📒 Files selected for processing (1)

• .github/workflows/codeChecks.yml (3 hunks)

🧰 Additional context used

🧠 Learnings (3)

📓 Common learnings

Learnt from: xenOs76
Repo: xenOs76/https-wrench PR: 16
File: devenv.nix:626-626
Timestamp: 2025-12-18T19:13:24.036Z
Learning: In the xenOs76/https-wrench repository's devenv.nix file, the `run-go-tests` command is intentionally excluded from the `enterTest` flow because Go unit tests are executed separately via GitHub Actions workflow (codeChecks.yml). This separation avoids redundancy, with devenv tests focusing on integration and CLI tests while GitHub Actions handles unit tests.

Learnt from: xenOs76
Repo: xenOs76/https-wrench PR: 16
File: devenv.nix:151-157
Timestamp: 2025-12-18T19:12:22.181Z
Learning: In the xenOs76/https-wrench repository, the `tests/` directory in devenv.nix is ephemeral and no files within it are expected to persist. It's acceptable to remove the entire directory as part of cleanup operations.

Learnt from: xenOs76
Repo: xenOs76/https-wrench PR: 10
File: internal/requests/requests_test.go:918-997
Timestamp: 2025-11-29T14:05:35.000Z
Learning: In the https-wrench tool test suite (xenOs76/https-wrench repository), the user wants to be reminded in the future about potentially adding MinVersion enforcement to TLS configurations in test code, once legacy server compatibility becomes less critical.

📚 Learning: 2025-12-18T19:13:24.036Z

Learnt from: xenOs76
Repo: xenOs76/https-wrench PR: 16
File: devenv.nix:626-626
Timestamp: 2025-12-18T19:13:24.036Z
Learning: In the xenOs76/https-wrench repository's devenv.nix file, the `run-go-tests` command is intentionally excluded from the `enterTest` flow because Go unit tests are executed separately via GitHub Actions workflow (codeChecks.yml). This separation avoids redundancy, with devenv tests focusing on integration and CLI tests while GitHub Actions handles unit tests.

Applied to files:

• .github/workflows/codeChecks.yml

📚 Learning: 2025-12-18T19:12:22.181Z

Learnt from: xenOs76
Repo: xenOs76/https-wrench PR: 16
File: devenv.nix:151-157
Timestamp: 2025-12-18T19:12:22.181Z
Learning: In the xenOs76/https-wrench repository, the `tests/` directory in devenv.nix is ephemeral and no files within it are expected to persist. It's acceptable to remove the entire directory as part of cleanup operations.

Applied to files:

• .github/workflows/codeChecks.yml

⏰ 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). (1)

• GitHub Check: devenv_tests

🔇 Additional comments (2)

.github/workflows/codeChecks.yml (2)

48-69: LGTM: devenv_tests job structure is correct.

The job dependency on go_tests ensures Go unit tests pass before running integration/CLI tests, which aligns with the separation of concerns. The devenv setup and test execution steps are properly configured.

Based on learnings, this maintains the intentional separation where Go unit tests run via GitHub Actions while devenv tests focus on integration and CLI validation.

---

21-21: Remove this comment—both Go versions 1.24 and 1.25 are valid and officially released.

Go 1.24 was released in February 2025 with multiple patch versions (1.24.1 through 1.24.11) released through December 2025, and Go 1.25.5 was released December 2, 2025. Both versions are stable, production-ready releases supported by the Go team.

[xenOs76]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.