An in-range update of @nuxtjs/sentry is breaking the build π¨
greenkeeper opened this issue Β· 2 comments
The dependency @nuxtjs/sentry was updated from 3.2.2
to 3.2.3
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@nuxtjs/sentry 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
- β codecov/project: 84.50% (+0.00%) compared to 848c868 (Details).
- β test-screenshot: null
- β npm audit: There are 1 failures, 0 warnings, and 0 notices.
- β test-unit (windows-latest): null
- β test-unit (macos-latest): null
- β test-unit (ubuntu-latest): null
- β lint (windows-latest): null
- β lint (macos-latest): null
- β lint (ubuntu-latest): null
Commits
The new version differs by 10 commits.
d8546a5
chore(release): 3.2.3
0ff5969
fix(types): add types for process.sentry (#153)
8ffce3a
fix: router.base not taken into account when releasing source maps (#152)
2ea40df
refactor: convert module's code to ES imports/exports (#151)
438ba50
chore(deps): update all non-major dependencies (#141)
8e3e4d1
fix: don't set urlPrefix for release on server (#150)
146ff20
fix: allow string to webpackConfig.include (#149)
c71d848
fix: enable source maps on server also
215c308
fix: release failure with non-standard directory structure
f78d7b6
fix: don't use Proxy to avoid problems with IE11 compatibility
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 π΄
After pinning to 3.2.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
dependency
@nuxtjs/sentry was updated from3.2.3
to3.2.4
.
Your tests are still failing with this version. Compare changes