-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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: remove dependency causing semantic-release to fail #23142
Conversation
Thanks for taking the time to open a PR!
|
@@ -2,6 +2,7 @@ | |||
"name": "@cypress/angular", | |||
"version": "0.0.0-development", | |||
"description": "Test Angular Components using Cypress", | |||
"private": true, |
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.
Should have been marked as private since we haven't released yet 😅
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.
Good catch!
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.
Looks good!
@@ -2,6 +2,7 @@ | |||
"name": "@cypress/angular", | |||
"version": "0.0.0-development", | |||
"description": "Test Angular Components using Cypress", | |||
"private": true, |
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.
Good catch!
Test summaryRun details
View run in Cypress Dashboard ➡️ Flakiness
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
User facing changelog
na
Additional details
Semantic release has been failing, possibly due to the semantic-release bump a few weeks ago. Hard to verify since we haven't had a passing
npm-release
job in a while. The problem was due to peer-deps from the@cypress/code-coverage
package innpm/vue
. Removing this allowed thenpm-release
job to move pass the error occurring in the@semantic-release/npm prepare
plugin (I verified by sshing into the last masternpm-release
job and runningyarn npm-release
. The tokens were out of date so no packages were published).We weren't verifying the results of
code-coverage
for the vue cypress tests, and it makes more sense in a system test anyway. In fact, we aren't even running thenpm/vue
cypress tests on CI right now. Going to follow up on this.Steps to test
No easy way to test this, since running
yarn npm-release
locally is mostly stubbed. I had to ssh into circleci to verify the behavior.How has the user experience changed?
na
PR Tasks
cypress-documentation
?type definitions
?