retract v1.9.0

[joe-bowman]

1. Summary

Fixes build issue with v1.9.0; retracts v1.9.0.

Summary by CodeRabbit

• Chores
  • Retracted release v1.9.0 from availability; consumers will no longer resolve or fetch this version.
  • No impact to runtime features or behavior; existing installations remain unaffected.
  • Previously supported versions continue to resolve and operate as expected.
  • Build and tooling workflows that pin to other versions are unaffected.

[coderabbitai]

Walkthrough

Added a new retract directive in go.mod to retract version v1.9.0 due to a build issue with a dependency. Existing retract for v1.7.0 remains. No other sections of go.mod were modified.

Changes

Cohort / File(s)	Summary
Module metadata go.mod	Added retract v1.9.0 // build issue with dependency; retained existing retract v1.7.0 // safety bug. No changes to require/replace sections.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I thump my foot at version nine,
A carrot-redact, a tidy line.
Hop past the snag, keep modules clean,
Two notes in go.mod, crisp and lean.
With ears up high, I ship just fine.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch retract-v1.9.1

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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 (2)

go.mod (2)

393-393: Fix typo in comment: “dependendy” → “dependency”.

Minor nit to keep go.mod tidy and professional.

Apply this diff:

-retract v1.9.0 // build issue with dependendy
+retract v1.9.0 // build issue with dependency

---

392-394: Add a reference for traceability (issue/PR link).

Helps future readers understand the rationale behind the retraction.

Optionally update the comment to include the PR number:

-retract v1.9.0 // build issue with dependency
+retract v1.9.0 // build issue with dependency (see #1956)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between cdc71fc and a4245fd.

📒 Files selected for processing (1)

• go.mod (1 hunks)

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

• GitHub Check: test quicksilver (amd64, windows)
• GitHub Check: test quicksilver (darwin, arm64)
• GitHub Check: test quicksilver (amd64, linux)
• GitHub Check: lint
• GitHub Check: Analyze

🔇 Additional comments (2)

go.mod (2)

392-394: LGTM: Retract directive is correct and matches the PR objective.

Syntax is valid, placement at the bottom is fine, and this achieves the stated goal of retracting v1.9.0.

---

393-393: No v1.9.0 pre-release tags detected
All Git tags matching v1.9.0* (e.g. -rc, -beta) are absent, so only the existing

retract v1.9.0 // build issue with dependency

entry is needed.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.62%. Comparing base (cdc71fc) to head (a4245fd).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1956      +/-   ##
==========================================
- Coverage   57.64%   57.62%   -0.02%     
==========================================
  Files         171      171              
  Lines       15291    15291              
==========================================
- Hits         8815     8812       -3     
- Misses       5705     5707       +2     
- Partials      771      772       +1     

Flag	Coverage Δ
unittests	57.62% <ø> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.