An in-range update of browser-sync is breaking the build π¨
The dependency browser-sync was updated from 2.25.0 to 2.26.0.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
browser-sync is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
Commits
The new version differs by 12 commits.
ec7b82dv2.26.0f83ba7elerna whitespace to allow publishd7ca182v2.25.3-alpha.0257fba6fix: Removing default logger prefix [BS] - fixes #1607cc8dfadv2.25.2-alpha.0d4c58b8Merge branch 'master' into 1591-prevent-reloadabc0124Merge branch 'johanblumenberg-patch-1'dacfc8bfix: proxy: case insensitive matching of cookie domain - fixes #160611729ccfix: bump chokidar fixing fsevents build - closes #16139eafa03v2.25.1-alpha.00d4ab81chore: move cypress to top-level dep06ee1b7fix: Unexpected Page Reload after Pausing in Debugger - fixes #1591
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot :palm_tree:
After pinning to 2.25.0 your tests are passing again. Downgrade this dependency π.
- The
dependencybrowser-sync was updated from2.26.0to2.26.1.
Your tests are passing again with this update. Explicitly upgrade to this version π
- The
dependencybrowser-sync was updated from2.26.1to2.26.2.
Your tests are passing again with this update. Explicitly upgrade to this version π
- The
dependencybrowser-sync was updated from2.26.2to2.26.3.
Your tests are passing again with this update. Explicitly upgrade to this version π
Release Notes for 2.26.0 -> 2.26.3
fixes
Commits
The new version differs by 6 commits.
924d5e7v2.26.3d60cd91fix: application/wasm support in Chrome - fixes #1598f95dd7av2.26.29f3fea4deps: npm audit fixes across all packages - fixes #1618cf7cb3ev2.26.10a2ff5afix: deps - ensure previous users of browser-sync-client are not affected by new structure - fixes #1615
See the full diff