The --use-artifact-bundle option was never meant to be part of the public API. Passing it may have a harmful effect, since it causes artifact bundles to be uploaded, even when the Sentry server does not declare support for receiving them in the chunk upload options. However, we should keep the option around, as the JS bundler plugins use the option to ensure artifact bundles are sent. Removing the option completely (or making it a no-op) would potentially break compatibility with some versions of self-hosted Sentry, since support for receiving artifact bundles seems to have been added to Sentry before this support was declared in the chunk upload options.
The
--use-artifact-bundleoption was never meant to be part of the public API. Passing it may have a harmful effect, since it causes artifact bundles to be uploaded, even when the Sentry server does not declare support for receiving them in the chunk upload options. However, we should keep the option around, as the JS bundler plugins use the option to ensure artifact bundles are sent. Removing the option completely (or making it a no-op) would potentially break compatibility with some versions of self-hosted Sentry, since support for receiving artifact bundles seems to have been added to Sentry before this support was declared in the chunk upload options.