20.12.2013, 00:13, "Sam Roberts" <[email protected]>: > On Wed, Dec 18, 2013 at 5:42 PM, Alex Kocharin <[email protected]> wrote: > >> So if something needs to be republished, maintainer will be >> forced to change version number (or add a build number although it's now >> ignored by npm). > > I've found force republish invaluable in the last weeks when publishes > to npmjs.org silently half-work, leaving the tarball missing from > cloudfare. I'd prefer a build number, but like you say, its not > respected by npm, and I'm not really happy with having to use patch > number as a publish-retry number.
What about using fourth number for it? Like "1.2.3-4"? If you document out what this versioning means, it'll be fine since immutability is much more valuable here than strict adherence to semver (which is proven to be a bad default anyway). -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
