meta: Update changelog for 2.0.0 (#253)

Author: Luca Forstner

CHANGELOG.md

@@ -4,6 +4,29 @@
 
 - "You know what they say ‘Fool me once, strike one, but fool me twice… strike three.’" — Michael Scott
 
+## 2.0.0
+
+Version 2.0.0 marks the official release of the `@sentry/vite-plugin`, `@sentry/esbuild-plugin` and `@sentry/rollup-plugin` packages.
+They are now considered stable.
+
+For the `@sentry/webpack-plugin` this is a major release with breaking changes.
+Please refer to the [migration guide](https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/main/MIGRATION.md) for instructions on how to upgrade.
+
+- feat(core): Add `deleteFilesAfterUpload` option (#244)
+- feat(core): Implements rewrite sources for debug ID upload (#243)
+- fix(core): Account for undefined release name values (#251)
+- fix(webpack): Inject different debug IDs for different bundles (#242)
+- ref(core): Add new options type for future use (#216)
+- ref(core): Extract debug ID injection into separate plugins (#230)
+- ref(core): Extract debug ID sourcemap upload into a separate plugin (#231)
+- ref(core): Extract release injection into separate plugins (#218)
+- ref(core): Extract release management into a separate plugin (#232)
+- ref(core): Extract telemetry into a separate plugin (#234)
+- ref(core): Switch to v2 options (#237)
+- ref(core): Use debug ID as filename for upload (#247)
+- ref(core): Use factory function to create individual plugins (#229)
+- ref: Remove `injectReleasesMap` option (#236)
+
 ## 0.7.2
 
 - fix(core): Use createRequire to not use built-in require in ESM (#212)

MIGRATION.md

@@ -2,14 +2,16 @@
 
 This document serves as a migration guide, documenting all breaking changes between major versions of the Sentry bundler plugins.
 
-## Unreleased
+## Upgrading to 2.x
 
 - Removed `injectReleasesMap` option. If you need to inject values based on the build, please use your bundler's way of injecting values ([rollup](https://www.npmjs.com/package/@rollup/plugin-replace), [vite](https://vitejs.dev/config/shared-options.html#define), [webpack](https://webpack.js.org/plugins/define-plugin/), [esbuild](https://esbuild.github.io/api/#define)).
 - The minimum compatible version of rollup is version `3.2.0`.
 - Removed functionality for the `releaseInjectionTargets` option.
 - `@sentry/bundler-plugin-core` will no longer export the individual plugins but a factory function to create them.
+- Removed `customHeader` option in favor of `headers` option which allows for multiple headers to be attached to outgoing requests.
+- The `cliBinaryExists` function was renamed to `sentryCliBinaryExists`
 
-## [Unreleased] Upgrading from 1.x to 2.x (Webpack Plugin Only)
+## Upgrading from 1.x to 2.x (Webpack Plugin Only)
 
 Version 2 of `@sentry/webpack-plugin` is a complete rewrite of version 1, relying on bundler-agnostic code (based on [unjs/unplugin](https://github.com/unjs/unplugin)). While we tried to keep changes to v1 of the webpack plugin minimal, a adjustments are nevertheless necessary:
 
@@ -20,13 +22,15 @@ In version 2, you simply need to call a function and pass the initialization opt
 
 ```js
 // old initialization:
+import SentryCliPlugin from "@sentry/webpack-plugin";
 new SentryCliPlugin({
-  include: "./dist",
+  // ... options
 });
 
 // new initialization:
+import { sentryWebpackPlugin } from "@sentry/webpack-plugin";
 sentryWebpackPlugin({
-  include: "./dist",
+  // ... options
 });
 ```
 
@@ -58,30 +62,6 @@ sentryWebpackPlugin({
 });
 ```
 
-### Replacing `entries` option with `releaseInjectionTargets`
-
-Previously, the `entries` option was used to filter for _entrypoints_ that the plugin should inject the release into.
-Releases were only injected into entrypoint files of a bundle.
-In version 2, releases are injected into every module that is part of a bundle.
-Don't worry, your bundler will only include the injected release code once.
-Instead of using the `entries` option to filter for _entrypoints_, the `releaseInjectionTargets` option can now be used to filter for _modules_ that the plugin should inject the release into.
-Matching behaviour stays the same.
-
-### Injecting `SENTRY_RELEASES` Map
-
-Previously, the webpack plugin always injected a `SENTRY_RELEASES` variable into the global object which would map from `project@org` to the `release` value. In version 2, we made this behaviour opt-in by setting the `injectReleasesMap` option in the plugin options to `true`.
-
-The purpose of this option is to support module-federated projects or micro frontend setups where multiple projects would want to access the global release variable. However, Sentry SDKs by default never accessed this variable so it would require manual user-intervention to make use of it. Making this behaviour opt-in decreases the bundle size impact of our plugin for the majority of users.
-
-### Removal of the `customHeader` option
-
-The `customHeader` was used to attach an additional header to outgoing requests to Sentry when uploading source maps.
-This option has been removed in favor of the `headers` option which allows for attaching multiple headers.
-
-### Renaming of `cliBinaryExists` to `sentryCliBinaryExists`
-
-The `cliBinaryExists` function was renamed to `sentryCliBinaryExists`.
-
 ## Upgrading from 0.3.x to 0.4.x
 
 ### Replacing default exports with named exports