release: integrate xyz #191
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
davidchambers
force-pushed
the
release
branch
from
6bb2125 to
dafe19c
Compare
SimonRichardson
approved these changes
Oct 23, 2016
|
@SimonRichardson, could you run this to grant me permission to upload tarballs to the registry? $ npm owner add davidchambers fantasy-land |
|
Sure, will have to be later, I've not got my computer with me atm On Sun, 23 Oct 2016, 19:30 David Chambers, [email protected] wrote:
|
|
No worries, Simon. Hardy added me as an owner. I'll publish the release notes shortly. :) |
rjmk
added a commit
to rjmk/fantasy-land
that referenced
this pull request
Nov 12, 2016
* 'master' of github.com:fantasyland/fantasy-land: (29 commits) Version 2.1.0 Add Alt, Plus and Alternative specs (fantasyland#197) Use uppercase letters for Type representatives in laws (fantasyland#196) Fix id_test and argument order in laws (fantasyland#193) Version 2.0.0 Another go at updating dependencies (fantasyland#192) release: integrate xyz (fantasyland#191) test: remove unnecessary lambdas (fantasyland#190) require static methods to be defined on type representatives (fantasyland#180) lint: integrate ESLint (fantasyland#189) Enforce parametricity (fantasyland#184) readme: tweak signatures to indicate that methods are not curried (fantasyland#183) Fix reduce signature to not use currying (fantasyland#182) Link to dependent specifications (fantasyland#178) Add Fluture to the list of implementations (fantasyland#175) laws/functor: fix composition (fantasyland#173) laws/monad: fix leftIdentity (fantasyland#171) Minor version bump bower: add bower.json (fantasyland#159) Fix chainRec signature to not use currying (fantasyland#167) ...
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using xyz to release new versions of this package will remove many sources of human error from the process. It will also make releasing new versions very convenient, as one will simply run one of the following commands:
$ npm run-script release-major$ npm run-script release-minor$ npm run-script release-patchThis will:
master.npm testexits successfully."version"field in package.json.Version X.Y.Z.vX.Y.Zpointing to the commit.npm publish.I've used xyz countless times over the past two and a half years. It's rock solid. It's not Windows-compatible, but I imagine that's not a problem.