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
bindown needs a way to determine which bindown versions a config file will work with.
This will come up in #161 because adding {{ .microArch }} to a template will cause earlier bindown versions to error.
This won't be a big deal for individual repositories because you can simply not add features before you start using a version of bindown that handles them. However template repositories like https://github.com/WillAbides/bindown-templates should be able to signal that they don't support older versions of bindown.
Options
bindown_version
Add something like bindown_version: '>= 4.3.0' to the config and fail with a message to upgrade when reading a config file from a version of bindown that doesn't meet the constraint.
I think this will work for non-breaking changes like #161 where new functionality is added, but this doesn't work when something is removed.
It would also be difficult to figure out what value to use for bindown_version when writing a config file.
config_version
Similar to api_version but it's about config files instead.
The text was updated successfully, but these errors were encountered:
bindown needs a way to determine which bindown versions a config file will work with.
This will come up in #161 because adding
{{ .microArch }}
to a template will cause earlier bindown versions to error.This won't be a big deal for individual repositories because you can simply not add features before you start using a version of bindown that handles them. However template repositories like https://github.com/WillAbides/bindown-templates should be able to signal that they don't support older versions of bindown.
Options
bindown_version
Add something like
bindown_version: '>= 4.3.0'
to the config and fail with a message to upgrade when reading a config file from a version of bindown that doesn't meet the constraint.I think this will work for non-breaking changes like #161 where new functionality is added, but this doesn't work when something is removed.
It would also be difficult to figure out what value to use for
bindown_version
when writing a config file.config_version
Similar to
api_version
but it's about config files instead.The text was updated successfully, but these errors were encountered: