The upgrade-commands setting for deploys was a bit awkward. It required each library to configure and know about the special upgrade needs of each library. In addition, adding new specific settings (like enabling changelog updates) would be difficult.
This new feature reads a .pco-release.config.yml file at the root of consumer repos when deploying. If there is a file, it will read it and use its configuration to override some settings.
Currently, this allows for specifying the upgrade_command, which it also uses string replacement to allow for specifying the version and package name.
For instance, tapestry-react will add the file like this:
The
upgrade-commandssetting for deploys was a bit awkward. It required each library to configure and know about the special upgrade needs of each library. In addition, adding new specific settings (like enabling changelog updates) would be difficult.This new feature reads a
.pco-release.config.ymlfile at the root of consumer repos when deploying. If there is a file, it will read it and use its configuration to override some settings.Currently, this allows for specifying the
upgrade_command, which it also uses string replacement to allow for specifying the version and package name.For instance, tapestry-react will add the file like this:
In the future, I hope to also use the config for changelog update settings.