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

Fix version checks in .availableHelper and transform-runtime definitions. #8659

Merged
merged 1 commit into from Sep 11, 2018

Conversation

loganfsmyth
Copy link
Member

Q                       A
Fixed Issues? Fixes #1, Fixes #2
Patch: Bug Fix?
Major: Breaking Change?
Minor: New Feature?
Tests Added + Pass? Yes
Documentation PR Link
Any Dependency Changes?
License MIT

The comments in the code pretty much explain why this change is needed. I think this is enough to fix the issue, but it's actually a little difficult to be 100% sure since I don't entirely trust semver anymore.

As noted by the changes in the tests, this is definitely something that we need to fix in order for things to function properly. On 7.0.0 essentially any helper will show up as available, unfortunately.

An alternative fix here would be to change transform-runtime and external-helpers to stop passing 7.0.0-beta.0 as their default version, but I think the approach here is better?

Since we've landed so much and might just straight to 7.1.0, I'm actually tempted to branch and release a 7.0.1 with just this applied on top, so people have more of a chance to get updated to a version with a functional .availableHelper(). On the fence there though.

@loganfsmyth loganfsmyth added the PR: Bug Fix 🐛 A type of pull request used for our changelog categories label Sep 10, 2018
@babel-bot
Copy link
Collaborator

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/9062/

Copy link
Member

@nicolo-ribaudo nicolo-ribaudo left a comment

Choose a reason for hiding this comment

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

+1 for the 7.0.1 branch release. Maybe we could also release the regressions fixes we have already merged.

@hzoo
Copy link
Member

hzoo commented Sep 10, 2018

Ok, I made 7.0.patch branch off of 7.0.0. We can merge this and cherry pick this and other patches onto that branch and release it as a 7.0.1 (a one-off)? Then land the next minor/releases from master as usual.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated A closed issue/PR that is archived due to age. Recommended to make a new issue PR: Bug Fix 🐛 A type of pull request used for our changelog categories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants