-
-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upload sourcemaps issue with latest 2.4.0 CLI release #1283
Comments
Thanks for the report, should be fixed in #1284, will release a patched version once it's merged. |
Thanks @kamilogorek, once a patch is available we can retest. Obviously we have a workaround for now with pinning the version |
It should do that from the very beginning, but it somehow snuck into the |
Yah this issue blocked a release for us and helped uncover an unpinned dependency. Thanks for reporting @spra85!!! |
The issue should be fixed in |
Environment
How do you use Sentry?
Sentry SaaS (sentry.io)
Which SDK and version?
Javascript Sentry CLI, latest - 2.4.0
Steps to Reproduce
Basic command in our CI build is below, where
REACT_APP_COMMIT
is set to essentially Git SHA for releasesentry-cli releases files $REACT_APP_COMMIT upload-sourcemaps build/static/js
Our installation of Sentry-CLI used this command from the README:
With the most recent version bump, the command above started failing with "release not found".
Pinning the version to the one right before does work, which implies a 2.4.0 change caused this.
It's possible we weren't correctly using it in the first place and 2.4.0 is more strict; for instance, from the docs it suggests this -
With 2.4.0, does the CLI expect that we would first need to create a new release, prior to trying to upload the source map whereas previous versions allowed that to happen in a single step/command?
Expected Result
The source map would upload
Actual Result
The text was updated successfully, but these errors were encountered: