Skip to content
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

fix(deps): update dependency @sentry/cli to v2 #269

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 7, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/cli (source) 1.74.4 -> 2.5.2 age adoption passing confidence

Release Notes

getsentry/sentry-cli

v2.5.2

Compare Source

Various fixes & improvements

v2.5.1

Compare Source

Various fixes & improvements

v2.5.0

Compare Source

Various fixes & improvements

v2.4.1

Compare Source

Various fixes & improvements

v2.4.0

Compare Source

Various fixes & improvements

v2.3.1

Compare Source

Various fixes & improvements

v2.3.0

Compare Source

Various fixes & improvements

v2.2.0

Compare Source

Various fixes & improvements

v2.1.0

Compare Source

Source Maps Upload Check "y-tho" (ongoing)

Problem statement:

Uploading source maps is a common source of frustration. Source maps are also one of the great value adds to our in product experience. We want to automate supporting customers with frequent issues.

https://docs.sentry.io/platforms/javascript/sourcemaps/troubleshooting_js/

*Outcome: *

Developers will be provided with a tool to help them discover any issues they may have when uploading source maps

Sentry support will have a tool and docs to suggest to customers to hopefully first discover issues, and second at least know what their problem is NOT.

Key measurements:

  • qualitative: Is this useful for customers and support
  • quantitative: Can we try to influence the number of Zendesk tickets
  • quantitative: Can we influence the resolution time of source maps related Zendesk tickets

Can we find a way to track in zendesk the number of times the sentry-cli “y-tho“ functionality was useful

Additional

This is something users would run locally so I do not think we can track usage exactly what was not covered in y-tho

  • Verify your source maps are built correctly
  • Verify your source maps work locally
  • Verify your source files are not too large
    • this is a fuzzy requirement today in sentry
  • Verify artifacts are not gzipped
  • Verify workers are sharing the same volume as web (if running self-hosted Sentry via Docker)
  • Should spit out an easily readable and easily copy and paste - to put into ZenDesk or elsewhere for support colleagues

Possible second milestone:

https://github.com/getsentry/rust-sourcemap/tree/master/cli

  • In sentry error incorrect source map location
  • this helps when producing sourcemaps locally then line and column
  • this verify that it resolves locally
    • if yes then it is a problem in between on sentry server side or upload
    • 1st Verifies what you upload to sentry is exactly what you upload to sentry
    • 2nd step from “y-tho” ensure previous steps are not for waste
  • What is being automated?
    • on release page you have your files (release artificats)
      • download
      • manually check the line number matches the error
      • if correct then data is correct
      • then you know an error with cli and not with the source maps that were uploaded

By: @​kamilogorek (#​1235)

Various fixes & improvements

v2.0.4

Compare Source

Various fixes & improvements

v2.0.3

Compare Source

Various fixes & improvements
  • ref: Make --header a global flag so its position independent (#​1194)
  • ref: Restore monitors as hidden command w. integration tests (#​1196)
  • ref: Restore bash-hook as hidden command w. integration tests (#​1197)

v2.0.2

Compare Source

Various fixes & improvements

v2.0.1

Compare Source

Various fixes & improvements

v2.0.0

Compare Source

This is the first, long-overdue major release in over 5 years of sentry-cli's life.
Some APIs were removed, some reworked, some newly added.

Most of introduced API changes are backward compatible through hidden aliases, so there is no immediate need for users developing 3rd party tools to make all the changes immediatelly.
We do however encourage everyone to do it sooner or later, as deprecated items will be removed in the next major releases.

Breaking changes are denotated with (breaking) tag, and appropriate required changes are provided for each entry.

New APIs
  • feat: Add debug-files command, which is a joined functionality of difutil and upload-dif commands.
  • feat: Add deploys command, which was extracted from releases deploys subcommand.
  • feat: Add files command, which was extracted from releases files subcommand.
  • feat: Add sourcemaps upload command, which was extracted from releases files upload-sourcemaps subcommand.
  • feat: Add sourcemaps resolve command.
  • feat: Allow for specifying global --header argument, which supports multiple occurences, to configure outgoing requests
  • feat: Implement global --quiet/--silent flags to allow silencing stdout output (This flag is currently implemented only for selected subcommands)
Removed APIs
  • ref: Remove react-native codepush subcommand (use react-native appcenter instead) (breaking)
  • ref: Remove react-native-gradle and react-native-xcode commands (use react-native gradle and react-native xcode instead) (breaking)
  • ref: Remove crash_reporting related code and with_crash_reporting crate feature (no required changes) (breaking)
  • ref: Remove SENTRY_NO_PROGRESS_BAR env var in favor of SENTRYCLI_NO_PROGRESS_BAR (rename env variable) (breaking)
  • ref: Hide difutil id subcommand (use debug-files check instead)
  • ref: Hide upload-dsym command (use debug-files upload instead)
  • ref: Make releases upload-sourcemaps --rewrite a default behavior now
  • ~ref: Remove upload-dsym command (use debug-files upload instead) (breaking)~ restored in 2.0.2 as hidden alias
  • ~ref: Remove difutil id subcommand (use debug-files check instead) (breaking)~ restored in 2.0.2 as hidden alias
  • ~ref: Remove monitors command (support for this feature has been dropped) (breaking)~ - restored in 2.0.3 as hidden command
  • ~ref: Remove bash-hook command (use 1.x if you still need the functionality) (breaking)~ - restored in 2.0.3 as hidden command
Breaking Changes
  • ref: Update minimal required node version to v12 (update node version) (breaking)
  • ref: Rename --header argument of releases files upload command to --file-header (rename flag) (breaking)
  • ref: Rename CUSTOM_HEADER to SENTRY_HEADER and defaults.custom_header to http.header (rename env variable or update config file) (breaking)
  • ref: Make ignore-empty for releases set-commits a default behavior and hide --ignore-empty flag (remove --ignore-empty usage) (breaking)
Various fixes & improvements
  • feat: Implement --quiet flag for releases upload-sourcemaps command
  • feat: Implement --quiet flag for difutil check command
  • ref: Make --auth-token a global argument
  • ref: Make all ProgressBar instances and logs always write to stderr
  • ref: Migrate error handling from failure to anyhow crate

v1.74.5

Compare Source

Various fixes & improvements
  • deps: Add resolution to bump ansi-regex to version ^3.0.1 (#​1281)
  • ref: Increase TempFile robustness on Windows (#​1256)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented May 7, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
prom ✅ Ready (Inspect) Visit Preview Aug 17, 2022 at 1:03PM (UTC)

@renovate renovate bot force-pushed the renovate/sentry-cli-2.x branch from 01187dc to 253ab16 Compare May 10, 2022 22:05
@renovate renovate bot force-pushed the renovate/sentry-cli-2.x branch from 253ab16 to 9ccbba0 Compare May 24, 2022 13:03
@renovate renovate bot force-pushed the renovate/sentry-cli-2.x branch from 9ccbba0 to 337abab Compare June 17, 2022 13:00
@renovate renovate bot force-pushed the renovate/sentry-cli-2.x branch from 337abab to d28cd49 Compare June 23, 2022 13:44
@renovate renovate bot force-pushed the renovate/sentry-cli-2.x branch from d28cd49 to cad0a73 Compare July 1, 2022 12:14
@renovate renovate bot force-pushed the renovate/sentry-cli-2.x branch from cad0a73 to fea469a Compare July 7, 2022 12:20
@renovate renovate bot force-pushed the renovate/sentry-cli-2.x branch from fea469a to cfdf0df Compare July 7, 2022 23:34
@renovate renovate bot force-pushed the renovate/sentry-cli-2.x branch from cfdf0df to 7c030fc Compare July 13, 2022 13:41
@renovate renovate bot force-pushed the renovate/sentry-cli-2.x branch from 7c030fc to 3fa8c9a Compare July 14, 2022 12:23
@renovate renovate bot changed the title fix(deps): update dependency @sentry/cli to v2 fix(deps): update dependency @sentry/cli to v2 - autoclosed Jul 20, 2022
@renovate renovate bot closed this Jul 20, 2022
@renovate renovate bot deleted the renovate/sentry-cli-2.x branch July 20, 2022 12:12
@renovate renovate bot changed the title fix(deps): update dependency @sentry/cli to v2 - autoclosed fix(deps): update dependency @sentry/cli to v2 Jul 20, 2022
@renovate renovate bot reopened this Jul 20, 2022
@renovate renovate bot restored the renovate/sentry-cli-2.x branch July 20, 2022 14:46
@renovate renovate bot force-pushed the renovate/sentry-cli-2.x branch from 3fa8c9a to 123dcd7 Compare July 20, 2022 16:42
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.

0 participants