💡 Feature request
Feature Name
Internal version consistency
The Desired Behavior
When I use https://github.com/mage-os/github-actions/blob/main/fix-magento-install/action.yml#L12 It uses mage-os/github-actions/get-magento-version@main. This should instead be mage-os/github-actions/get-magento-version@1.4.0 (or whatever the current version is). Then, when we do a PR like #125 it should automatically bump this version.
Your Use Case
Developers really shouldn't be relying on main. It's not supposed to be that stable. We should document the currently leading version, allowing main to be a little less stable.
Prior Work
Release please supports with in .release-please-config.json with extra-files
{
...
"extra-files": [
"path/to/file"
],
...
}
You simply have to add # x-release-please-version on the line with the version in it.
💡 Feature request
Feature Name
Internal version consistency
The Desired Behavior
When I use https://github.com/mage-os/github-actions/blob/main/fix-magento-install/action.yml#L12 It uses
mage-os/github-actions/get-magento-version@main. This should instead bemage-os/github-actions/get-magento-version@1.4.0(or whatever the current version is). Then, when we do a PR like #125 it should automatically bump this version.Your Use Case
Developers really shouldn't be relying on
main. It's not supposed to be that stable. We should document the currently leading version, allowingmainto be a little less stable.Prior Work
Release please supports with in
.release-please-config.jsonwithextra-files{ ... "extra-files": [ "path/to/file" ], ... }You simply have to add
# x-release-please-versionon the line with the version in it.