<p dir="auto">This is with Julia 0.6</p>
<p dir="auto">I tagged one or two packages, and then tried to published them. This failed, likely because PkgDev couldn't properly authorize with Github. I then tagged and published the same package from Julia 0.4, where everything went fine. Now I see this in Julia 0.6:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="julia&gt; Pkg.update()
INFO: Updating METADATA...
WARNING: Cannot perform fast-forward merge."><pre class="notranslate"><code class="notranslate">julia&gt; Pkg.update()
INFO: Updating METADATA...
WARNING: Cannot perform fast-forward merge.
</code></pre></div>
<p dir="auto">This warning has been there for a few days. How do I avoid it? Is there a way to do this automatically, or do I need to low-level git repo management? Would a hard git reset to the upstream master branch be appropriate, or can this lose data? (I would reset only the metadata repo, leaving my packages alone.)</p>
<p dir="auto">I am making this an issue instead of a question on the mailing list because I think that tagging and publishing should be mainstream (not expert) actions, and Pkg and PkgDev should handle common error conditions automatically, or if not, should at least detect them and point to respective documentation.</p>
<p dir="auto">This is admittedly likely to affect only a small number of people, but I wonder about whether it's reasonable to support <code class="notranslate">publish</code>ing branches that are not <code class="notranslate">metadata-v2</code>. Now that I'm back working on packages, I often have 3 or more simultaneous PRs in to METADATA, and to avoid duplication I create separate branches. Even if we get to the point where Travis isn't the bottleneck in METADATA PRs, it's been demonstrated repeatedly that these PRs are still worth reviewing, so it seems likely that many PRs will be out there for at least several hours.</p>