Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG] Breaking Change in v1.25.0 release from v1.24.2
See original GitHub issueThe exported function used to be addTestCommand, now that has been made private, and a new function addTestCommands is exported, so code relying on the exported API surface is breaking on the new version.
The fix is I guess to change to use addTestCommands but this is not documented in the release notes, not sure if there are any differences we should be aware of.
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:13 (9 by maintainers)
Top Results From Across the Web
Kubernetes Removals and Major Changes In 1.25
Kubernetes v1.25 includes several major changes and one major removal. ... changes, which unfortunately would have been breaking changes.
Read more >Kubernetes v1.25.0 is live! - Google Groups
Kubernetes v1.25.0 has been built and pushed using Golang version 1.19. The release notes have been updated in CHANGELOG-1.25.md, ...
Read more >Release notes - Calico - Tigera
Remove apiserver PodSecurityPolicy, as policy/v1beta1 is removed in Kubernetes v1.25+ calico #6270 (@caseydavenport). Bug fixes. General. Set IPIPMode and ...
Read more >kubernetes/CHANGELOG-1.25.md at master
21, and with the release of v1.25, it has been removed. The updates required to improve its usability would have introduced breaking changes,...
Read more >Confluent CLI Release Notes
Fix a bug causing repeated tags in confluent asyncapi export ... Guide for a full list of breaking changes and details regarding differences...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@mxschmitt is working on better error messaging in the case of version mismatch (https://github.com/microsoft/playwright/pull/16475), but I’m trying to understand how we get into the version mismatch state, so we can add docs and/or fixes as appropriate to prevent getting into it in the first place. Thanks for your patience with all the questions 😃 (I don’t want you to hit it again next time we release!)
This usually happens when playwright-core and @playwright/test have different versions. npm ci/npm i after aligning the versions should fix it.