Fix version and tag about d HOT 5 CLOSED

@franz-josef-kaiser I stopped doing that, as adding release always needs to be done manually.
Why it's important for you? You certainly have valid point, but I'd like to understand for what reasons devs use that feature (it's npm where versions are released not github)

from d.

When I switch releases in a package manager, then it's easier to have both the plain resources (git, zip) and as well the package manager packages. Also npm shrinkwrap complained about a pkg that used your package and it was unable to nail down the version (using a 6.x Nodejs version).

from d.

Also npm shrinkwrap complained about a pkg that used your package and it was unable to nail down the version (using a 6.x Nodejs version).

That's insteresting, do you suggest that npm shrinkwrap relies on github releases? It would be a big surprise to me.

from d.

npm shrinkwrap relies on github releases?

I am not completely sure if it does that. Aside from Composer, all other package manager internals are unknown to me. I just came here as the npm debug stacktrace pointed its trace back to this plugin. Package managers normally are capable using different mechanisms of delivery to use fallbacks in case some route does not work out: streams, tarballs, zips, vcs checkouts, you choose.

Btw, if you do not have a tag on GitHub and do not want to push one, you can simply open the releases tab, enter a version number and then just (as per the docs) get a new tag created for you.

from d.

I just came here as the npm debug stacktrace pointed its trace back to this plugin.

npm for sure doesn't depend on github releases. I'm closing it as it's for sure not relevant to your issue

from d.