dc/ng2-file-upload
4
0
Fork 0
Code Issues 395 Pull Requests 27 Packages Projects Releases 4 Wiki Activity

Update zone.js to version 0.6.17 🚀 #364

Closed
greenkeeperio-bot wants to merge 1 commits from greenkeeper-zone.js-0.6.17 into development
pull from: greenkeeper-zone.js-0.6.17
merge into: dc:development
Conversation 0 Commits 1 Files Changed 1 +1 -1
greenkeeperio-bot commented 2016-08-22 22:46:08 +00:00 (Migrated from github.com)
Copy Link

Hello lovely humans,

zone.js just published its new version 0.6.17.

State Update 🚀
Dependency zone.js
New version 0.6.17
Type devDependency

This version 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 zone.js.
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.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

The new version differs by 39 commits .

  • f57fc18 chore: release v0.6.17
  • 382182c fix: IE10/11 timeout issues.
  • 55f8150 chore: Release v0.6.16
  • d38ccde fix(jasmine): spelling error of 'describe' in jasmine patch prevented application of sync zone
  • d4dd351 chore: more correct test for jasmine
  • 396942b fix(patchProperty): return null as the default value (#413)
  • 3b4c20b fix(browser): use XMLHttpRequest.DONE constant on target instead of the global interface (#395)
  • 2d4ff65 fix long-stack-trace zone will not render correctly when reject a promise (#403)
  • 02a41c0 chore(release): version bump and dist for 0.6.15
  • ff88bb4 fix(tasks): do not drain the microtask queue early.
  • d4a1436 fix(tasks): do not drain the microtask queue early.
  • 5e3c207 fix: broken build. (#406)
  • fe76168 chore: rename proxy for consistency
  • 76acf6e chore(release): version bump and dist for 0.6.14
  • 3a054be feat(jasmine): patch jasmine to understand zones.

There are 39 commits in total. See the full diff.

This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

Hello lovely humans, [zone.js](https://www.npmjs.com/package/zone.js) just published its new version 0.6.17. <table> <tr> <th align=left> State </th> <td> Update :rocket: </td> </tr> <tr> <th align=left> Dependency </td> <td> zone.js </td> </tr> <tr> <th align=left> New version </td> <td> 0.6.17 </td> </tr> <tr> <th align=left> Type </td> <td> devDependency </td> </tr> </table> This version 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 zone.js. 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. Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and while I’m just a bot, there is a group of people who are happy to teach me new things. [Let them know](https://github.com/greenkeeperio/greenkeeper/issues/new). Good luck with your project :sparkles: You rock! :palm_tree: --- The new version differs by 39 commits . - [`f57fc18`](https://github.com/angular/zone.js/commit/f57fc1870bfbbe36566d2f6acfa435fea63617d4) <code>chore: release v0.6.17</code> - [`382182c`](https://github.com/angular/zone.js/commit/382182cbeba37417bb4a42f4b3f21f859909cb2a) <code>fix: IE10/11 timeout issues.</code> - [`55f8150`](https://github.com/angular/zone.js/commit/55f815017df6bbda23eb0d1f61795f6f0412f51e) <code>chore: Release v0.6.16</code> - [`d38ccde`](https://github.com/angular/zone.js/commit/d38ccde70c4be28c303b8860254fb171e53e58ff) <code>fix(jasmine): spelling error of 'describe' in jasmine patch prevented application of sync zone</code> - [`d4dd351`](https://github.com/angular/zone.js/commit/d4dd351fa3f4acd5906663e675e3297d70583c13) <code>chore: more correct test for jasmine</code> - [`396942b`](https://github.com/angular/zone.js/commit/396942ba6b84afe34facd94c5f320d1baeb04198) <code>fix(patchProperty): return null as the default value (#413)</code> - [`3b4c20b`](https://github.com/angular/zone.js/commit/3b4c20ba6c695c535aff86b1ec47f03b33049e67) <code>fix(browser): use XMLHttpRequest.DONE constant on target instead of the global interface (#395)</code> - [`2d4ff65`](https://github.com/angular/zone.js/commit/2d4ff654119497f19dcd15dfe1ceb66da7c1eac9) <code>fix long-stack-trace zone will not render correctly when reject a promise (#403)</code> - [`02a41c0`](https://github.com/angular/zone.js/commit/02a41c0a04f1cdd032915448652cf2dd48893fbc) <code>chore(release): version bump and dist for 0.6.15</code> - [`ff88bb4`](https://github.com/angular/zone.js/commit/ff88bb43d29711cd6d6c575f6855590455463ae3) <code>fix(tasks): do not drain the microtask queue early.</code> - [`d4a1436`](https://github.com/angular/zone.js/commit/d4a143699eb301d3dc338b4f41be6fad99917609) <code>fix(tasks): do not drain the microtask queue early.</code> - [`5e3c207`](https://github.com/angular/zone.js/commit/5e3c207072f82cb6619240a1aa31c4a0f82fb9f3) <code>fix: broken build. (#406)</code> - [`fe76168`](https://github.com/angular/zone.js/commit/fe7616828a663dd6c699fcc0d29ee555d3227330) <code>chore: rename proxy for consistency</code> - [`76acf6e`](https://github.com/angular/zone.js/commit/76acf6ed9028a0895af55db36c2a872362f98dad) <code>chore(release): version bump and dist for 0.6.14</code> - [`3a054be`](https://github.com/angular/zone.js/commit/3a054be7837e4c1cd12bad76f69904e303a82c47) <code>feat(jasmine): patch jasmine to understand zones.</code> There are 39 commits in total. See the [full diff](https://github.com/angular/zone.js/compare/5f366a1ca0ee00046375a25af25105fb5e66da24...f57fc1870bfbbe36566d2f6acfa435fea63617d4). --- This pull request was created by [greenkeeper.io](https://greenkeeper.io/). <sub>Tired of seeing this sponsor message? :zap: `greenkeeper upgrade`</sub>

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
dependencies
Pull requests that update a dependency file
 duplicate
enhancement
greenkeeper
help wanted
in progress
invalid
need to reproduce
question
status: pending
wontfix
No Label greenkeeper
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
allan medjedovic root sabhas
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dc/ng2-file-upload#364
Delete Branch "greenkeeper-zone.js-0.6.17"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?