🚀 feature request

Relevant Rules

This is a feature request for the Gazelle plugin.

Description

Right now the Gazelle plugin puts an integrity hash at the bottom of its gazelle_python.yaml manifest file. It appears that this sum is a hash of the manifest file itself. Any time any package is added or removed, or a package version changes, this sum is recalculated. This makes it difficult to use tools like Renovate to upgrade our Python packages, because if it wants to upgrade multiple libs the PRs conflict with each other: each one modifies that sum separately.

Describe the solution you'd like

I am curious if the sum can just be removed from the file. Could the manifest test instead just recalculate what the file should look like and then check if the file on disk matches? This is how e.g. the requirements.in -> requirements.txt calculation happens, and so you hit merge conflicts if alphabetically adjacent packages get upgraded, but in the usual case this avoids merge conflicts.

Describe alternatives you've considered

Right now it's just a lot of rebasing and recalculating this hash.

Thanks!