v0.25.1

• Fixed CI deployment script

v0.25.0

• Make yarn-bundle-entry.js executable

  Daniel Lo Nigro - Fri, 12 May 2017 10:10:36 -0700

• improved error message (#3269)

  Konstantin Raev - Fri, 12 May 2017 17:15:09 +0100

• Remove warning spam during install with file mutex (#3165)

  Matt Traynham - Fri, 12 May 2017 16:54:20 +0100

• added check on response code on publish cli command to accomodate additional registries (#3149)

  Mason Richins - Fri, 12 May 2017 16:50:05 +0100

• Switch to micromatch: fixes #3336 (#3339)

  • Trim patterns before generating RegExp
    Test suite now passes

• (BREAKING) Allow prerelease versions when checking peer deps (#3361)

  James Ide - Fri, 12 May 2017 16:19:53 +0100

  • Allow prerelease versions when checking peer deps
    Uses lower-level APIs in node-semver to allow prerelease versions when
    checking peer deps. This honors the intent of library authors e.g. when they
    write a React component that asks for "react": ">=15.0.0" they're saying OK
    with [email protected] (partly because the React team specifically has said that
    if you don't have any warnings in version N, then version N+1 should work for
    you). By extension and modulo bugs, [email protected] works too (if the user
    explicitly installs it).
    Test Plan: Added unit tests for the new semver utility.
    Tested in a real project that uses React 16.0.0-alpha.11 and verified I didn't
    get any peer dep warnings that usually appear from libraries that ask for
    "react": ">=15.0.0". Downgraded React to 0.14.0 (too low) and saw peer dep
    warnings come back as expected.

  • Tighten up upper bounds so that "2.0.0-pre" doesn't match "^1.0.0"
    node-semver converts ~ and ^ ranges into pairs of >= and < ranges but the
    upper bounds don't properly exclude prerelease versions. For example, "^1.0.0"
    is converted to ">=1.0.0 <2.0.0", which includes "2.0.0-pre" since prerelease
    versions are lower than their non-prerelease counterparts. As a practical
    workaround we make upper-bound ranges exclude prereleases and convert "<2.0.0"
    to "<2.0.0-0", for example.
    Added unit tests as well.

• modify git ref parsing to not error on non-matching lines #3325 (#3351)

  Jeff Valore - Fri, 12 May 2017 16:14:00 +0100

• Include requested url in cantRequestOffline error (#3335)

  Andres Suarez - Fri, 12 May 2017 14:54:58 +0100

• workspaces: first phase: install node_modules aggregated from all workspaces (#3229)

  Konstantin Raev - Thu, 11 May 2017 17:53:36 +0100

• Fix Travis OSX tests (#3379)

  PICHOU Kyâne - Thu, 11 May 2017 15:33:20 +0100

• Fix yarn "entrypoint" shell script (#3362)

  PICHOU Kyâne - Thu, 11 May 2017 14:46:24 +0100

  #3260 PR broke the bin/yarn shell script (see issue #3321)
  #3338 tried to fix it in a improper way
  This way should work.

• use yarn instead of npm everywhere is possible aka Eating your own dog food (#3374)

  Simon Vocella - Wed, 10 May 2017 19:02:52 +0100

• Implements the enable-meta-folder (#3367)

  Maël Nison - Wed, 10 May 2017 19:01:08 +0100

  • Implements the enable-meta-folder

  • Adds enable-meta-folder support to yarn-error.log

• upgrade babel-core (#3366)

  Simon Vocella - Wed, 10 May 2017 17:22:45 +0100

• Updates the yarn-create prefix (#3358)

  Maël Nison - Tue, 9 May 2017 13:56:39 +0100

• Add a more useful error message when we cache a broken tarball (#3355)

  Roman Sandler - Tue, 9 May 2017 13:55:45 +0100

  It looks like there should be an error handler that reports the
  fetchErrorCorrupt string, but instead an error from tar-stream
  is being
  returned without the filename.

• Include yarn and node versions in yarn.lock (#3265)

  Christopher Stott - Mon, 8 May 2017 17:48:25 +0100

  Sometimes it is helpful for automated tooling to know the version of
  yarn and
  nodejs that was used in the environment that last modified the
  yarn.lock file.

  For example, this allows CI platforms to automatically ensure the
  same
  versions of yarn and node are used in CI as locally.
  This functionality can be disabled by adding to .yarnrc
  yarn-disable-lockfile-versions true

• link bins of transitive deps to top level (#3310)

  Jeff Valore - Mon, 8 May 2017 16:56:15 +0100

  • #2874 link bins of transitive deps to top level

• Don't always prune mirrored scoped packages resolved by URLs (#3342)

  Nicholas Bollweg - Mon, 8 May 2017 16:53:32 +0100

• Adds yarn create (#3244)

  Maël Nison - Fri, 5 May 2017 10:26:04 +0100

• Fixes offline resolution for absolute Windows paths (#3319)

  Maël Nison - Thu, 4 May 2017 17:48:17 +0100

v0.24.4

Fixes:

• Make bin/yarn-bundle-entry.js (bin/yarn.js in the tarball) executable
• Fix yarn "entrypoint" shell script (#3362)

v0.24.3

• Updates the prefix used for yarn-create packages; was yarn-create-, is now simply create-
• Adds a enable-meta-folder option to move the integrity file and possibly others into a common directory

v0.24.2

• Adds yarn create

v0.24.1

Same as 0.24.0, triggered a new release for CI

v0.24.0: Fixes offline resolution for absolute Windows paths (#3319)

• Fix offline resolution (#3311)

  Maël Nison - Thu, 4 May 2017 13:46:13 +0100

• Add vendor informations to licences ls command (#3292)

  Matthias Lochbrunner - Wed, 3 May 2017 11:39:25 +0100

• Correctly handle installationMethod when using bundled build (#3113)

  Daniel Lo Nigro - Tue, 2 May 2017 15:29:36 +0100

• Better use of English in why output (#3280)

  Ben - Tue, 2 May 2017 12:11:50 +0200

• Add tests for global command (#3238)

  Simon Vocella - Tue, 2 May 2017 10:30:20 +0100

• Resolve Git dependencies offline if tarball is available. (#3000)

  Raymond Wang - Mon, 1 May 2017 20:00:56 +0100

  When running yarn offline, Git dependencies get trapped in
  hasHTTPCapabiity
  even though resolveOverHTTP defaults to returning
  the tarball. This change
  allows us to bypass that step altogether
  if the tarball already exists.

• add some tests for link/unlink command (#3293)

  Simon Vocella - Mon, 1 May 2017 17:18:28 +0100

• remove duplication in tests/commands/pack.js (#3291)

  Simon Vocella - Mon, 1 May 2017 17:10:45 +0100

• Clean Homebrew Git repo before committing. Fixes #3275

  Daniel Lo Nigro - Sat, 29 Apr 2017 17:05:33 -0700

• pack: include contents of directories in files field (#3175)

  Joseph Frazier - Fri, 28 Apr 2017 17:41:51 +0100

• extract the reporter out of integrity checker (#3248)

  Simon Vocella - Wed, 26 Apr 2017 17:48:29 +0100

• Adding verbose output for config file search (#3236)

  Dennis Webb - Wed, 26 Apr 2017 16:19:00 +0100

• use close instead of finish event for file copy completion (#3234)

  Daniel Pihlstrom - Wed, 26 Apr 2017 16:17:24 +0100

  Windows Defender updates timestamps on files immediately after a write stream
  closes. Moving utimes update to after the file has closed corrects this issue.

• Fix a couple of lint warnings for unused variables (#3232)

  Lukas Spieß - Wed, 26 Apr 2017 16:15:26 +0100

• Add .yarnrc env config option (#3218)

  Sebastian McKenzie - Wed, 26 Apr 2017 16:12:25 +0100

• Fix typo: specifally -> specifically (#3246)

  Joseph Frazier - Wed, 26 Apr 2017 15:57:50 +0100

• Change use_winpty logic in bin/yarn to just look at YARN_FORCE_WINPTY in environment (#3245)

  mikew - Wed, 26 Apr 2017 15:57:30 +0100

• Fix local tarball file resolution (#3221)

  Maël Nison - Wed, 26 Apr 2017 15:51:28 +0100

• Fixes for running with artifactory 4.14.1 (#3172)

  Rogério Chaves - Tue, 25 Apr 2017 16:04:09 +0100

  • Add fallback vdn header for repositories that do not support it

  • Add auth even if registry url is https and archive url is http

• When in flat mode don't add unused dependencies - fixes #2781 (#3251)

  Sebastian McKenzie - Tue, 25 Apr 2017 12:06:38 +0100

• Move integrity artifacts tracking to separate method - fixes #3247 (#3250)

  Sebastian McKenzie - Tue, 25 Apr 2017 12:06:06 +0100

• Ref #2165 - file-resolver should invalidate cache with a new hash (#2860)

  Matt Traynham - Mon, 24 Apr 2017 22:31:45 +0100

  • file-resolver should invalidate cache with a new hash everytime

  • Add/update tests for file protocol cache busting with force flag

  • Fixing cache test and adding comment on size of cache directory.

• Fix global module executable path on Windows (#3233)

  Daniel Lo Nigro - Mon, 24 Apr 2017 10:56:39 +0100

• rename skipIntegrity in skipIntegrityCheck (#3239)

  Simon Vocella - Mon, 24 Apr 2017 10:48:40 +0100

• Use npm's node-gyp if available, otherwise automatically install node-gyp (#3240)

  Daniel Lo Nigro - Mon, 24 Apr 2017 10:44:48 +0100

  • Attempt to install node-gyp if it's required but missing

  • Try to use node-gyp version from npm

  • Trailing commas

• feat(Upgrade): add scope flag to the upgrade command (#3190)

  Joge97 - Mon, 24 Apr 2017 08:53:16 +0200

• accept 1ms difference in filedates as equal on windows (#3235)

  Daniel Pihlstrom - Sun, 23 Apr 2017 19:03:44 -0700

  a nodejs issue causes certain dates to be off by 1ms after calling utimes
  See: nodejs/node#12607

• Put build artifact tracking in integrity file (#3224)

  Sebastian McKenzie - Sat, 22 Apr 2017 16:45:03 +0100

  • Put build artifact tracking in integrity file

  • fix lint

• fix lint warning (#3226)

  Vladimir Agafonkin - Sat, 22 Apr 2017 16:44:18 +0100

• Move inquirer code to console reporter (#3207)

  Rifat Nabi - Sat, 22 Apr 2017 15:52:10 +0100

  • Move inquirer code to console reporter

  • Fix double ctrl+c to exit problem

• partially revert #2657 to fix add command test (#3222)

  Vladimir Agafonkin - Fri, 21 Apr 2017 21:21:46 +0100

• Do not test new version with pkg.version (#3103)

  Michael Heuberger - Thu, 20 Apr 2017 19:19:38 -0700

  See issue 3011 for details. Leave it to
  npm registry to validate the version
  number.

• Adds clean-mirror.sh to scripts (#3179)

  Maël Nison - Thu, 20 Apr 2017 19:08:06 -0700

• Fix yarn pack to always include the file in the "main" field (#3092)

  Joseph Frazier - Thu, 20 Apr 2017 17:48:00 -0700

  • Test that yarn pack always includes the file in the "main" field
    This is for compatibility with npm, which [specifies] that:

• Optimize buildActionsForCopy routine (#2657)

  Vladimir Agafonkin - Thu, 20 Apr 2017 16:20:48 -0700

  • optimize buildActionsForCopy routine

  • more resilient sync in util.fs, add comments

• Use an alias system instead of camelCase function (#3101)

  Simon Vocella - Thu, 20 Apr 2017 16:26:59 +0100

  • • move aliases to unsupported aliases
  • tests properly camelised comand
  • tests properly command with hyphen
  • move generation of documentation in src/cli/commands/index.js
  • move every command related stuff in src/cli/commands/index.js
  • tests some corner cases
  • delete every camelCase use in src/cli/commands/index.js and

  src/cli/commands/help.js

  • fix typo and initialize commands in a clearer way

• add hasWrapper function in clean and remove command (#3205)

  Simon Vocella - Thu, 20 Apr 2017 11:32:13 +0100

• Ensure that every command has setFlags and hasWrapper functions (#3105)

  Simon Vocella - Thu, 20 Apr 2017 11:08:43 +0100

  • ensure that every command has setFlags function

  • ensure that every command has hasWrapper function

• Hide Activity/Progress Output in JSONReporter with --no-progress Flag (#3158)

  Alec Merdler - Thu, 20 Apr 2017 10:59:39 +0100

• Avoids using Array.prototype.includes since it is not avaialble in node 4. (#3139)

  Miguel Madero - Thu, 20 Apr 2017 10:56:12 +0100

  Fixes #3138

• Use gunzip-maybe instead of reimplementing (#2971)

  Victor Noël - Tue, 18 Apr 2017 17:05:37 +0100

• Better match npm's SCP vs SSH URL heuristic (#3147)

  Kornel - Tue, 18 Apr 2017 17:02:32 +0100

  Fixes #3146

• Fix typo: inlude -> include (#3171)

  Joseph Frazier - Tue, 18 Apr 2017 16:37:40 +0100

• Fix typo: definently -> definitely (#3173)

  Joseph Frazier - Tue, 18 Apr 2017 16:37:16 +0100

• Fix bug when cannot set a config value to empty string (#3018)

  Igor Redchuk - Tue, 18 Apr 2017 11:52:34 +0100

  • Fixes regression introduced in PR #2440
  • Related to #2434

• Automatically update Homebrew package when new versions are released (#3083)

  Daniel Lo Nigro - Thu, 13 Apr 2017 08:19:09 -0700

  Closes #2841

• Fix resolver incorrect lockfile (issue #2629) (#3106)

  Konstantin Raev - Wed, 12 Apr 2017 18:28:42 +0100

  • wip fixing resolver when lockfile has incorrect semver entries

  • Fixes incorrect entries in lockfiles
    Fixes #2629.
    If lockfile pattern does not match a version it will be ignored
    and re-resolved

• supported smaller package metadata API (#3112)

  [Konstantin R...

v0.23.4

• Fix tarball file (#3221)

v0.23.3

Fixes an issue with Node 4 (#3139)

v0.22.1

0.22.1