-
Task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
Bumps [@sentry/webpack-plugin](https://github.com/getsentry/sentry-javascript-bundler-plugins) from 3.0.0 to 3.1.2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/releases"><code>@​sentry/webpack-plugin</code>'s releases</a>.</em></p>
<blockquote>
<h2>3.1.2</h2>
<ul>
<li>deps: Bump <code>@sentry/cli</code> to <code>2.41.1</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/671">#671</a>)</li>
</ul>
<h2>3.1.1</h2>
<ul>
<li>
<p>fix(core): Disable release creation and source maps upload in dev mode (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/666">#666</a>)</p>
<p>This fix disables any external calls to the Sentry API for managing releases or uploading source maps, when detecting that the plugin is running in dev-mode. While this rarely actually happened,
it also polluted the dev server output with unnecessary logs about missing auth tokens, which shouldn't
be required in dev mode.</p>
</li>
</ul>
<h2>3.1.0</h2>
<ul>
<li>feat(webpack): Gate forced process exit behind experimental flag (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/663">#663</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/main/CHANGELOG.md"><code>@​sentry/webpack-plugin</code>'s changelog</a>.</em></p>
<blockquote>
<h2>3.1.2</h2>
<ul>
<li>deps: Bump <code>@sentry/cli</code> to <code>2.41.1</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/671">#671</a>)</li>
</ul>
<h2>3.1.1</h2>
<ul>
<li>
<p>fix(core): Disable release creation and source maps upload in dev mode (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/666">#666</a>)</p>
<p>This fix disables any external calls to the Sentry API for managing releases or uploading source maps, when detecting that the plugin is running in dev-mode. While this rarely actually happened,
it also polluted the dev server output with unnecessary logs about missing auth tokens, which shouldn't
be required in dev mode.</p>
</li>
</ul>
<h2>3.1.0</h2>
<ul>
<li>feat(webpack): Gate forced process exit behind experimental flag (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/663">#663</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/900341064e20483c1dd4fd58a194544f2d2da14a"><code>9003410</code></a> release: 3.1.2</li>
<li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/1063e0a2cd1093a7a33446b3930e6e77a43d2c0c"><code>1063e0a</code></a> meta: Update changelog for <code>3.1.2</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/672">#672</a>)</li>
<li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/cfb6fcc12b9900398c9f2c2643bf3ea6969fdcc9"><code>cfb6fcc</code></a> deps: Bump <code>@sentry/cli</code> to <code>2.41.1</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/671">#671</a>)</li>
<li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/27626a3688c32d92b87583f89a6217ff55ed8f3f"><code>27626a3</code></a> Merge branch 'release/3.1.1'</li>
<li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/0db92f683ab0a4952e6d1b32e75a43d938c2d52b"><code>0db92f6</code></a> release: 3.1.1</li>
<li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/8cdc739c168e66c1e85d6155ad15eb8516a44c0a"><code>8cdc739</code></a> meta: Add Changelog for 3.1.1 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/668">#668</a>)</li>
<li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/d39f50ebbcb9f2ea8743ce5aa13acf9c4a2dbbc6"><code>d39f50e</code></a> fix(core): Check for dev mode via <code>process.env.NODE_ENV</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/666">#666</a>)</li>
<li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/071fd5cc0b2d46c977df30b2d4fa08a52694415a"><code>071fd5c</code></a> Merge branch 'release/3.1.0'</li>
<li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/b2f807b2192ab965747301a06b5ecf6948ee72ef"><code>b2f807b</code></a> release: 3.1.0</li>
<li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/d57886dc724863669cb5c951cd055495b4cc5cb5"><code>d57886d</code></a> meta: Update changelog for 3.1.0 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/664">#664</a>)</li>
<li>Additional commits viewable in <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/compare/3.0.0...3.1.2">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
//: # (dependabot-automerge-start)
//: # (dependabot-automerge-end)
—
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
- mentioned on