Skip to content

test(ci): NODE 6 continuous integration #570

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

Closed
wants to merge 1 commit into from
Closed

Conversation

jkuri
Copy link
Contributor

@jkuri jkuri commented Apr 30, 2016

No description provided.

@@ -17,7 +17,7 @@
"url": "https://github.com/angular/angular-cli.git"
},
"engines": {
"node": ">= 4.1.0"
"node": ">= 5.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we want to exclude anyone still on node 4 even though were not running tests for it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hansl said that we don't support node 4 anymore.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

then leave it as is

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought you were asking about if we still tested on node 4. It's fine to keep node 4.1, unless there's a technical problem with this PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverted.

@jkuri jkuri force-pushed the node6 branch 6 times, most recently from f9c5b6c to 3de6cc4 Compare April 30, 2016 02:15
@@ -65,7 +65,7 @@
"exists-sync": "0.0.3",
"minimatch": "^3.0.0",
"mocha": "^2.4.5",
"mock-fs": "^3.8.0",
"mock-fs": "^3.9.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does this dependency need updating?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mike has told me it was to support node 6.

Copy link
Contributor Author

@jkuri jkuri Apr 30, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was the update I was waiting for, before it was not supporting node6.

@filipesilva
Copy link
Contributor

Lgtm if it passes tests. Seems to have an issue with OSX.

@jkuri jkuri force-pushed the node6 branch 21 times, most recently from cc02469 to cfaac57 Compare April 30, 2016 03:34
@jkuri jkuri force-pushed the node6 branch 6 times, most recently from 9dc0b79 to f30100f Compare April 30, 2016 04:04
@jkuri
Copy link
Contributor Author

jkuri commented May 16, 2016

Closing. @hansl will take over of this.

@jkuri jkuri closed this May 16, 2016
@jkuri jkuri deleted the node6 branch July 12, 2016 20:50
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants