Skip to content

t1441: unblock patch releases from historical preflight debt#4146

Merged
marcusquinn merged 2 commits intomainfrom
bugfix/t1441-release-preflight
Mar 11, 2026
Merged

t1441: unblock patch releases from historical preflight debt#4146
marcusquinn merged 2 commits intomainfrom
bugfix/t1441-release-preflight

Conversation

@marcusquinn
Copy link
Owner

Summary

  • Add a patch-specific release preflight that compares current findings against the latest tag instead of failing on historical repository debt.
  • Limit patch preflight checks to new secretlint findings and changed shell scripts, with a fallback to the full preflight when no baseline tag exists.
  • Expose a standalone preflight [major|minor|patch] command and route release through the bump-type-aware preflight path.

Closes #4145

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 11, 2026

Warning

Rate limit exceeded

@marcusquinn has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 3 minutes and 3 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.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ddbc59e4-b9f3-4da1-a19b-4ce296f230ab

📥 Commits

Reviewing files that changed from the base of the PR and between d650eb3 and 4a3abd7.

📒 Files selected for processing (1)
  • .agents/scripts/version-manager.sh
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch bugfix/t1441-release-preflight

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

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

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the release process by introducing a more intelligent and targeted preflight mechanism, particularly for patch releases. It shifts from a comprehensive historical check to a focused regression analysis, ensuring that only new issues introduced since the last release are flagged. This change aims to streamline patch releases by preventing them from being blocked by pre-existing issues, while also providing developers with a flexible command to run specific preflight checks.

Highlights

  • Patch Release Preflight: Implemented a patch-specific release preflight that compares current findings against the latest Git tag, avoiding historical repository debt.
  • Targeted Checks: Restricted patch preflight checks to new secretlint findings and modified shell scripts, with a fallback to full preflight if no baseline tag exists.
  • New Preflight Command: Introduced a standalone preflight [major|minor|patch] command and integrated it into the release command's preflight path.
Changelog
  • .agents/scripts/version-manager.sh
    • Refactored run_preflight_checks to support different bump types.
    • Added new functions for secretlint configuration, output normalization, and finding capture.
    • Implemented run_patch_release_preflight for targeted patch release checks.
    • Integrated the new preflight logic into the main release flow.
    • Exposed a new preflight command for direct execution of preflight checks.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions
Copy link
Contributor

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 402 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Wed Mar 11 17:14:48 UTC 2026: Code review monitoring started
Wed Mar 11 17:14:49 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 402

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 402
  • VULNERABILITIES: 0

Generated on: Wed Mar 11 17:14:51 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

@gemini-code-assist
Copy link

Warning

Gemini is experiencing higher than usual traffic and was unable to create the review. Please try again in a few hours by commenting /gemini review.

@github-actions
Copy link
Contributor

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 402 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Wed Mar 11 17:19:26 UTC 2026: Code review monitoring started
Wed Mar 11 17:19:27 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 402

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 402
  • VULNERABILITIES: 0

Generated on: Wed Mar 11 17:19:29 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

@sonarqubecloud
Copy link

@marcusquinn marcusquinn merged commit c3d583e into main Mar 11, 2026
12 checks passed
@marcusquinn marcusquinn deleted the bugfix/t1441-release-preflight branch March 11, 2026 17:23
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.

t1441: Unblock patch releases by reducing repo-wide preflight blocker debt

1 participant