Can't use a dynamic release-as config after v4 migration #1068
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
We have a use case of creating a hotfix release with a self calculated patch version, of which we need to pass to the action as the
release-as
config variable. This config variable is calculated dynamically and is not committed to the repository.v4 version requires users to use a config file to set the
release-as
config. And, config files cannot be read from the filesystem, and has to be committed to the repo and be fetched from a repo & branch ref. As for the hotfix use case, this config is a dynamic variable, and can't be committed to the repo. Therefore, we can't use a dynamicrelease-as
config after v4 migration.On a side note, if release-please upstream package would have supported loading config files from a local filesystem, we would not have this issue. It's reported separately on #1017.
Environment details
Steps to reproduce
release-please-config.hotfix.json
The text was updated successfully, but these errors were encountered: