dev- branch plugin forks being prompted for update I'm currently using a fork of a plugin for my site, and using a &quot;dev-[branch-name]&quot; version specification in the composer &quot;require&quot; block, with a &quot;vcs&quot; repository definition for the fork location on github - basically looks like:
&quot;repositories&quot;: [
  {
    &quot;type&quot;: &quot;vcs&quot;,
    &quot;url&quot;: &quot;https://github.com/[forked-account/plugin-name]&quot;
  }
],
&quot;require&quot;: {
  &quot;[original-account/plugin-name]&quot;: &quot;dev-branch-name&quot;
  ...
}
...

This worked fine for several months, but I'm suddenly now seeing a prompt to update to the latest version of the plugin on the author's &quot;master&quot; branch when running Craft update.  Has something changed with the requirements for the composer file version declarations for Craft to respect the &quot;dev-&quot; branch version as the preferred plugin version?
I experience the same with https://github.com/Saboteur777/craft-support forked from https://github.com/jasonmccallister/craft-support (which is a fork of https://github.com/lukeyouell/craft-support).
Using composer update will not change &quot;tracks&quot; to the original plugin, so you are safe to update, the notification is a minor annoyance, though.