Skip to content

Conversation

@rchl
Copy link
Member

@rchl rchl commented Feb 17, 2022

BREAKING CHANGE: To use the "publishRelease" option, it's now necessary to manually install the @sentry/webpack-plugin package as a dev dependency.

This is in response to Sentry change getsentry/sentry-webpack-plugin#343 which inadvertently made webpack dependencies get installed in production.

BREAKING CHANGE: To use the "publishRelease" option, it's now necessary
to manually install the @sentry/webpack-plugin package as a dev
dependency.
@codecov
Copy link

codecov bot commented Feb 17, 2022

Codecov Report

Merging #390 (b6fe2c9) into master (f72147f) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #390   +/-   ##
=======================================
  Coverage   71.42%   71.42%           
=======================================
  Files           1        1           
  Lines          49       49           
  Branches       23       23           
=======================================
  Hits           35       35           
  Misses         11       11           
  Partials        3        3           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f72147f...b6fe2c9. Read the comment docs.

@rchl
Copy link
Member Author

rchl commented Feb 20, 2022

While Sentry reverted their change, it is still technically more correct to list @sentry/webpack-plugin as a peer dependency as it's not required for normal operation of the module and should only really be required on building. This will also remove further dependencies from production.

* origin/master:
  fix(deps): update dependency @sentry/webpack-plugin to ^1.18.7 (#392)
@rchl rchl merged commit 0877174 into master Feb 20, 2022
@rchl rchl deleted the feat/peer branch February 20, 2022 20:04
rchl added a commit that referenced this pull request Feb 20, 2022
BREAKING CHANGE: To use the "publishRelease" option, it's now necessary
to manually install the `@sentry/webpack-plugin` package as a dev
dependency.
rchl added a commit that referenced this pull request Aug 3, 2022
BREAKING CHANGE: Make `@sentry/webpack-plugin` a peer dependency. To use the "publishRelease" option, it's now necessary to manually install that package as a dev dependency.
rchl added a commit that referenced this pull request Aug 3, 2022
)

BREAKING CHANGE: Don't include `@sentry/webpack-plugin` as a dependency. To use the "publishRelease" option, it's now necessary to manually install that package as a dev dependency.
rchl added a commit that referenced this pull request Aug 3, 2022
…390)

BREAKING CHANGE: Don't ship with `@sentry/webpack-plugin` as a dependency. To use the "publishRelease" option, it's now necessary to manually install that package as a dev dependency.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants