Does the plugin API version always match the Composer version? #10030
-
|
Based on renovatebot/renovate#11019: Composer automatically updates the So does the plugin API version always match the Composer version? Or phrased differently given the context of the mentioned ticket: can one safely determine the last Composer major+minor version which was used to update the lockfile? The change mentioned in the ticket (7dd95a7) implies this slightly since this plugin API version bump was published with the first RC of Composer 2.1. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
|
In short.. no. It only gets bumped when we do add features, so most likely it'll only at best match the major.minor version of the composer used. But if nothing changes for plugins most likely we will not even bump it, and it may remain at 2.1.0 for a while. I am not sure what you are trying to achieve here though? |
Beta Was this translation helpful? Give feedback.
-
|
runtime-api is the same deal yes. We'll introduce a new I also don't really see a perfect way out of this, sorry :) |
Beta Was this translation helpful? Give feedback.
-
|
No problem, you already helped me a lot. As mentioned I'll try to get this solved in Renovate itself. |
Beta Was this translation helpful? Give feedback.
-
|
Also #9963 sounds like it could actually help with my issue. We could then require e.g. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah that could be an option, although it's most likely to cause friction in the team and be quite annoying.. I wonder if it's really worse than dealing with the occasional bad update with the current setup, which I imagine would be rather infrequent. |
Beta Was this translation helpful? Give feedback.
-
|
You are probably right. I guess we'll just leave it as it is and see if we really encounter issues. We don't plan to lag behind Composer releases in our dev environment for too long anyways. |
Beta Was this translation helpful? Give feedback.
In short.. no. It only gets bumped when we do add features, so most likely it'll only at best match the major.minor version of the composer used. But if nothing changes for plugins most likely we will not even bump it, and it may remain at 2.1.0 for a while.
I am not sure what you are trying to achieve here though?