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

chore(deps): update CLI to v2.3.0 #10

Closed
wants to merge 1 commit into from

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Jul 6, 2022

Bumps tests/sentry-cli.properties from 2.0.0 to 2.3.0.

Auto-generated by a submodule dependency updater.

Changelog

2.3.0

Various fixes & improvements

  • fix: Allow for using --auth-token with login command (#1266) by kamilogorek
  • deps: Update all Rust dependencies (#1265) by kamilogorek
  • fix: Increase TempFile robustness on Windows (#1256) (#1263) by kamilogorek
  • ref: Remove confusing ending dots from command logs (#1261) by kamilogorek
  • fix: Correct typo in sourcemaps explain output (#1258) by huwq1987
  • fix: Use first frame that has context-line in explain (#1255) by kamilogorek
  • feat: Add send-envelope command (#1254) by kamilogorek

2.2.0

Various fixes & improvements

  • feat: Compute and upload il2cpp line mappings (#1248) by loewenheim
  • ref: Skip protected zip files when uploading debug files (#1245) by kamilogorek

2.1.0

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

  • ref: Change comment format for find_matching_artifact (#1243) by kamilogorek
  • ref: Log correct AppCenter error message (#1243) by kamilogorek
  • fix: Respect no-zips option for debug files upload (#1239) by saf-e
  • chore: fix recommended VS Code extension name (#1240) by vaind
  • ref: Rename VERSION to SENTRY_CLI_VERSION in install readme (#1227) by kamilogorek
  • feat: Add organizations list command (#1213) by kamilogorek
  • docs(cli): Sync get-cli readme with our docs; add version specifier (#1225) by kamilogorek
  • test: Add integration tests for projects command (#1212) by kamilogorek
  • fix: replace git.io links with redirect targets (#1209) by asottile-sentry

2.0.4

Various fixes & improvements

  • ref: Prevent vercel/nft and similar tools from including binary file in their bundles (#1207) by kamilogorek
  • ref: Use node-fetchv2 for the simplicity sake (#1206) by kamilogorek

2.0.3

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)

2.0.2

Various fixes & improvements

  • fix: Remove fetch.FetchError usage in favor of catch-all clause (#1193) by kamilogorek
  • ref: Restore and hide legacy aliases from 1.x for backward compatibility (#1192) by kamilogorek

2.0.1

Various fixes & improvements

  • fix: Allow hyphenated release names with any flags position (#1187) by kamilogorek

@github-actions github-actions bot force-pushed the deps/tests/sentry-cli.properties/2.3.0 branch from f5e5e73 to b6ee357 Compare July 6, 2022 20:28
@github-actions github-actions bot force-pushed the deps/tests/sentry-cli.properties/2.3.0 branch from b6ee357 to 9900cf9 Compare July 7, 2022 08:22
@github-actions github-actions bot force-pushed the deps/tests/sentry-cli.properties/2.3.0 branch from 9900cf9 to 0f4b4ca Compare July 7, 2022 08:32
@vaind vaind closed this Jul 7, 2022
@vaind vaind deleted the deps/tests/sentry-cli.properties/2.3.0 branch July 7, 2022 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants