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 and pin typescript to 2.6.1 #27

Closed
wants to merge 1 commit into from

Conversation

mightyiam
Copy link
Collaborator

Yeah, this is better. TypeScript do not adhere to semver in the language itself. Every single release, even patch, could break your compilation.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling a3c34b3 on mightyiam:typescript-update into 5ba15ac on tjoskar:master.

@@ -40,7 +40,7 @@
"npm-run-all": "^4.1.1",
"nyc": "^11.0.2",
"nyc-config-100": "^1.0.1",
"typescript": "^2.5.3"
"typescript": "2.6.1"
Copy link
Owner

Choose a reason for hiding this comment

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

I agree to update typescript but I do not see the point to pin it. We are using package-lock.json to lock all our dependencies.

@mightyiam
Copy link
Collaborator Author

mightyiam commented Dec 3, 2017 via email

@tjoskar
Copy link
Owner

tjoskar commented Dec 3, 2017

@mightyiam, I see but greenkeeper will run our test against every new version of typescript regardless if we have pin it or not. However, if we don't pin it Greenkeep will only create a PR if our test suite fails. If we pin it Greenkeep will create a PR for every new release regardless if the test suite passes or fails, or I'm I wrong?

@tjoskar
Copy link
Owner

tjoskar commented Dec 3, 2017

I close this but please let me know if there is any direct benefit of pinning typescript :)

@tjoskar tjoskar closed this Dec 3, 2017
@mightyiam
Copy link
Collaborator Author

TypeScript does not follow semver.

The recommendation there is to specify a MINOR version. I take it a step further to PATCH to be on the safe side.

While Greenkeeper may cause CI to run for any new version (I don't know exactly the behavior), what we desire is that a development environment will have the absolute (PATCH) latest TypeScript. That makes sense to me. For this, we have to pin it.

https://github.com/angular/angular/blob/1f5fa25583e01886313a2c14568d5c6da3a2d9ad/package.json#L101

https://github.com/cyclejs/cyclejs/blob/5be4faa0eac6f93470a25281bd6167a61bb0de93/package.json#L34

https://github.com/dojo/core/blob/a808fa0e09860aeb180c2359ee81eb1a814491fa/package.json#L56

tjoskar pushed a commit that referenced this pull request Dec 12, 2017
@tjoskar tjoskar mentioned this pull request Dec 12, 2017
tjoskar pushed a commit that referenced this pull request Dec 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants