Answers.Body: <p>I experience the same with <a href="https://github.com/Saboteur777/craft-support" rel="nofollow noreferrer">https://github.com/Saboteur777/craft-support</a> forked from <a href="https://github.com/jasonmccallister/craft-support" rel="nofollow noreferrer">https://github.com/jasonmccallister/craft-support</a> (which is a fork of <a href="https://github.com/lukeyouell/craft-support" rel="nofollow noreferrer">https://github.com/lukeyouell/craft-support</a>).</p>
  <p>Using <code>composer update</code> will not change &quot;tracks&quot; to the original plugin, so you are safe to update, the notification is a minor annoyance, though.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-11-06T03:39:25.697Z
Answers.Text: thanks otto.  yes, composer seems to respect it, but using craft update does not. problem is, it shows up in the dashboard as a plugin having an update available - easy for a client to accidentally update and blow away the customizations that have been made...
Answers.UserDisplayName: Jegra
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-11-07T13:36:47.473Z
Answers.Text: `craft update` would update to the "original" plugin?
  
  Regardless the answer I would definitely suggest to disable admin updates, which will prevent any accidental updates by the client.
Answers.UserDisplayName: Ottó Radics
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-11-09T13:46:50.157Z
Answers.Text: Opened a bug report: https://github.com/pixelandtonic/craftnet/issues/224
Answers.UserDisplayName: Ottó Radics
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-11-05T08:02:42.530Z
Answers.LastActivityDate: 2020-11-05T08:02:42.530Z
Answers.UserDisplayName: Ottó Radics
Body: <p>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:</p>
  <pre><code>&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;
    ...
  }
  ...
  </code></pre>
  <p>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?</p>
  
Tags: <plugin-development><updates><composer>
Title: dev- branch plugin forks being prompted for update
ThreadText: # dev- branch plugin forks being prompted for update
  
  (Asked by: username_0 on 2020-11-05)
  
  I'm currently using a fork of a plugin for my site, and using a "dev-[branch-name]" version specification in the composer "require" block, with a "vcs" repository definition for the fork location on github - basically looks like:
  
  ```
  "repositories": [
    {
      "type": "vcs",
      "url": "https://github.com/[forked-account/plugin-name]"
    }
  ],
  "require": {
    "[original-account/plugin-name]": "dev-branch-name"
    ...
  }
  ...
  
  ```
  
  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 "master" branch when running Craft update. Has something changed with the requirements for the composer file version declarations for Craft to respect the "dev-" branch version as the preferred plugin version?
  
  **Tags:** plugin-development, updates, composer
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-11-05. Score: 2
  
  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 "tracks" to the original plugin, so you are safe to update, the notification is a minor annoyance, though.
  
  > **Comments:**
  > **username_0**: thanks otto.  yes, composer seems to respect it, but using craft update does not. problem is, it shows up in the dashboard as a plugin having an update available - easy for a client to accidentally update and blow away the customizations that have been made...  
  > **username_1**: `craft update` would update to the "original" plugin?  Regardless the answer I would definitely suggest to disable admin updates, which will prevent any accidental updates by the client.  
  > **username_1**: Opened a bug report: https://github.com/pixelandtonic/craftnet/issues/224  
  
  ---
  
  