Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update cross-env to the latest version 🚀 #20

Merged
merged 1 commit into from
May 12, 2017

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented May 11, 2017

Version 5.0.0 of cross-env just got published.

Dependency cross-env
Current Version 4.0.0
Type devDependency

The version 5.0.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of cross-env.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


Release Notes v5.0.0

5.0.0 (2017-05-11)

Bug Fixes

  • bin: add a bin entry for cross-env-shell (9c4f3462)

Features

Breaking Changes

  • Scripts using quotes or escape sequences will see a difference in behavior.
    Switching to the second bin should resolve any issue.

Closes #99.

(d7b48d5c)

Commits

The new version differs by 4 commits0.

  • 9c4f346 fix(bin): add a bin entry for cross-env-shell
  • d7b48d5 feat(bin): two bins (shell, non-shell) (#104)
  • 3881423 feat: don't change colons on non-PATH/NODE_PATH on win32 (#107)
  • 6994a24 docs(contributors): add amilajack to contributors (#98)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 43c71d5 on greenkeeper/cross-env-5.0.0 into b97f7d6 on master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 43c71d5 on greenkeeper/cross-env-5.0.0 into b97f7d6 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 43c71d5 on greenkeeper/cross-env-5.0.0 into b97f7d6 on master.

@JLHwung JLHwung force-pushed the greenkeeper/cross-env-5.0.0 branch from 43c71d5 to f718093 Compare May 12, 2017 05:01
@coveralls
Copy link

coveralls commented May 12, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling f718093 on greenkeeper/cross-env-5.0.0 into b97f7d6 on master.

@JLHwung JLHwung merged commit 178779e into master May 12, 2017
@greenkeeper greenkeeper bot deleted the greenkeeper/cross-env-5.0.0 branch May 12, 2017 05:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants