You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This means projects using Hermit can and will be broken if a bad version of Hermit gets released to Stable channel.
One solution would be to set a custom env var HERMIT_DIST_URL like https://github.com/cashapp/hermit/releases/download/v0.31.1. But that has two problems:
This variable needs to be set before Hermit is actually invoked and loaded, which means that we need an external way to set it, other than the supported/recommended way in hermit.hclenv property.
That will quickly go out of sync, and users need to update it manually regularly.
I suggest that if a repo locks the default installation URL in bin/hermit to specific versions, that Renovate bot updates it during regular updates. This means:
Users will stay up to date.
No need for an external (additional to Hermit) solution to manage environment variables before Hermit gets loaded.
This change is backwards compatible. users can still stay on stable channel if they want, and the bot won't change it if so.
The text was updated successfully, but these errors were encountered:
Follow up from #342
The current Renovate plugin supports updating versions of the binaries, but not the version of the hermit binary itself.
This is usually specified in the
bin/hermit
file, and it defaults to using thestable
channel:This means projects using Hermit can and will be broken if a bad version of Hermit gets released to Stable channel.
One solution would be to set a custom env var
HERMIT_DIST_URL
likehttps://github.com/cashapp/hermit/releases/download/v0.31.1
. But that has two problems:hermit.hcl
env
property.I suggest that if a repo locks the default installation URL in
bin/hermit
to specific versions, that Renovate bot updates it during regular updates. This means:stable
channel if they want, and the bot won't change it if so.The text was updated successfully, but these errors were encountered: