docs(renovate): document hash fields not updated by custom manager#315
Conversation
…anager The Renovate-annotated version pins custom manager updates version strings only. Adjacent hash = "sha256-..." fields require nix-update automation (fix-renovate-hashes.yml) in each affected repo. Add this to the description so engineers know to wire up nix-update when adding new fetchPypi/fetchurl packages with Renovate annotations. Assisted-by: Claude <noreply@anthropic.com>
Summary of ChangesHello, 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 improves the documentation for the Nix custom regex manager within the Renovate configuration. By clarifying that Renovate only handles version strings and not hash fields, it helps prevent stale hash issues and guides maintainers on the necessary steps to maintain build integrity after automated version bumps. Highlights
Using Gemini Code AssistThe 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
Customization To customize the 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 Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. 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. A version bump is not the end, the hash remains, a broken friend. Update the workflow, fix the key, to keep the build in harmony. Footnotes
|
There was a problem hiding this comment.
Pull request overview
Documentation-only change clarifying that the custom Nix regex manager in the org-wide Renovate preset updates only version strings, not adjacent hash = "sha256-..." fields, and pointing maintainers to the per-repo fix-renovate-hashes.yml workflow plus the need to register new fetchPypi/fetchurl packages in the nix-update workflow and flake outputs.
Changes:
- Expands the
descriptionof the Nix custom regex manager to document the hash-update gap and remediation path.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
hash = "sha256-...") are NOT updated by Renovatefix-renovate-hashes.ymlin each repo for automated hash correctionfetchPypi/fetchurlpackages need to be added to both the nix-update workflow and flake packages outputWhy
Renovate's custom regex manager silently leaves hash fields stale after version bumps. Without this documentation, the gap is invisible — maintainers don't know to wire up hash automation when adding new Nix-packaged dependencies.
Test plan
Assisted-by: Claude noreply@anthropic.com