renovate: Revert postUpgradeCommand

[echarrod]

Removed

• postUpgradeCommand - only works on self-hosted
• Hoping Renovate adds the goModTidyAll option mentioned soon Indirect dependencies in dependent go modules need to be updated renovatebot/renovate#12999 (comment), then we won't have to do this manually

Summary by CodeRabbit

• Chores
  • Updated configuration by removing automated post-upgrade tasks and command permissions.
  • Only the designated reviewer remains specified in the settings.

[coderabbitai]

Walkthrough

This change updates the renovate.json configuration file by removing the postUpgradeTasks section, which previously executed a recursive go mod tidy command on directories containing go.mod files after dependency upgrades. Additionally, the allowedCommands array, which permitted the specific find command pattern used for these tasks, has also been deleted. The only remaining configuration now specifies "andrewwormald" as an additional reviewer. No changes were made to any exported or public entities.

Possibly related PRs

• renovate: Add post-update command to tidy modules #128: Removes the postUpgradeTasks section, directly reversing the configuration change that ran go mod tidy after upgrades.
• renovate: Add allowedCommands #131: Removes both the postUpgradeTasks section and the allowedCommands array, undoing the additions introduced in this PR.

Suggested reviewers

• andrewwormald

Poem

In the garden of code where configs grow,
A rabbit hopped by, with a tidy to throw.
Out went the tasks, no more commands to run,
Now the file is lighter, the cleanup is done.
With andrewwormald watching, the changes are clear—
Hippity-hop, the config’s in the clear! 🐇✨

---

📜 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 1f5a9ff and fbf504d.

📒 Files selected for processing (1)

• renovate.json (0 hunks)

💤 Files with no reviewable changes (1)

• renovate.json

---

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.
  • 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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in 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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud