Skip to content

[Mercure] Fix enable_profiler node position #672

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

Merged
1 commit merged into from
Nov 9, 2019
Merged

[Mercure] Fix enable_profiler node position #672

1 commit merged into from
Nov 9, 2019

Conversation

chalasr
Copy link
Member

@chalasr chalasr commented Nov 8, 2019

Q A
License MIT
Doc issue/PR -

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Pull request passes validation.

@dunglas
Copy link
Member

dunglas commented Nov 8, 2019

Actually enable_profiler should be in a 0.3 folder, because it's a new flag, and it breaks the stable version.

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Pull request does not pass validation.

@chalasr
Copy link
Member Author

chalasr commented Nov 8, 2019

Right, fixed!

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Pull request does not pass validation.

@chalasr chalasr force-pushed the mercure-fix branch 2 times, most recently from 682098f to 26c23cb Compare November 8, 2019 09:04
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Pull request does not pass validation.

@stof
Copy link
Member

stof commented Nov 8, 2019

The validation error is because the master branch has alias 1.0.x-dev, not 0.3.x-dev (which looks wrong to me btw, if you plan multiple 0.x releases before reaching 1.0, with BC breaks between them)

@stof
Copy link
Member

stof commented Nov 8, 2019

Also, why 0.3 ? There is no 0.2 release yet

@dunglas
Copy link
Member

dunglas commented Nov 8, 2019

You’re right, the next bundle version is 0.2 (I mixed with the library version). And you’re also right about the branch alias. Both the bundle and the lib must be updated.

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Pull request does not pass validation.

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Pull request does not pass validation.

@dunglas
Copy link
Member

dunglas commented Nov 9, 2019

This PR can now be merged (the CI will be green now).

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Pull request passes validation.

@chalasr
Copy link
Member Author

chalasr commented Nov 9, 2019

Green

ghost pushed a commit that referenced this pull request Nov 9, 2019
This pull request was closed.
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.

4 participants