Please don’t remove version tags from git repo
-
In our AWS environment, we load all plugins using composer. We update weekly (or more often) and use specific versions in our composer.json files so that we can revert to prior versions of our deployments and load the plugins that were current at that time (especially useful if we need to rollback a plugin update that failed in some way). This works great except for when a plugin developer removes a tagged version from their git repo. Specifically, we had the following in our composer.json file:
"wpackagist-plugin/social-networks-auto-poster-facebook-twitter-g": "4.2.2"
And this caused deployment of an autoscale to die with:
Problem 1 - The requested package wpackagist-plugin/social-networks-auto-poster-facebook-twitter-g 4.2.2 exists as wpackagist-plugin/social-networks-auto-poster-facebook-twitter-g[4.2.3, 1.6.1, 1.7.0, 1.9.13, 2.4.8, 2.5.5, 2.6.3, 2.7.14, 2.7.22, 3.0.9, 3.1.2, 3.2.3, 3.4.31, 3.8.8, dev-trunk] but these are rejected by your constraint.
This, in turn, woke me up way too early on a Saturday morning as the alarms went off.
We could fix this by changing the line in composer.json to read:
"wpackagist-plugin/social-networks-auto-poster-facebook-twitter-g": "~4.2.2"
(add a tilde) but then we would not be able to roll back as prior deployments would just load the latest plugin and that defeats the point of a roll back.
It’s a minor thing to most people, but for those of us who use composer, please don’t delete tagged versions once they have been published please?
Thanks
-A
- The topic ‘Please don’t remove version tags from git repo’ is closed to new replies.