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: update dependencies of npm/react-vue #15095
Conversation
BREAKING CHANGE: change of architecture for component testing
Thanks for taking the time to open a PR!
|
@@ -37,6 +36,7 @@ | |||
"@babel/preset-typescript": "7.10.4", | |||
"@bahmutov/cy-api": "1.4.2", | |||
"@bahmutov/cy-rollup": "2.0.0", | |||
"@cypress/webpack-dev-server": "0.0.0-development", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this work for the published package? Does semantic release automatically inject correct version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since webpack-dev-server is not published yet, this is the only version that yarn will accept.
I believe the dependencies to be updated by server automatically at release but I will check the script.
It's better to be safe than sorry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just checked, and it does do it for webpack-preprocessor.
We should be OK.
We can always deliver a new fixed version later by merging on master if it was not the case.
@@ -12,26 +12,26 @@ | |||
"watch": "tsc -w" | |||
}, | |||
"dependencies": { | |||
"@babel/plugin-transform-modules-commonjs": "7.10.4", | |||
"@cypress/code-coverage": "3.8.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that we are not connecting it by default anymore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... We are, but maybe we should not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ensure that any breaking change commits are properly formatted. feat: BREAKING CHANGE: vue
etc
BREAKING CHANGE: change of architecture for component testing