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-sdk to v2.22.0 #49

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 8, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sentry-sdk (changelog) ==2.15.0 -> ==2.22.0 age adoption passing confidence

Release Notes

getsentry/sentry-python (sentry-sdk)

v2.22.0

Compare Source

Various fixes & improvements

v2.21.0

Compare Source

Various fixes & improvements

v2.20.0

Compare Source

v2.19.2

Compare Source

Various fixes & improvements

v2.19.1

Compare Source

Various fixes & improvements

v2.19.0

Compare Source

Various fixes & improvements

v2.18.0

Compare Source

Various fixes & improvements

v2.17.0

Compare Source

Various fixes & improvements

v2.16.0

Compare Source

Integrations
  • Bottle: Add failed_request_status_codes (#​3618) by @​szokeasaurusrex

    You can now define a set of integers that will determine which status codes
    should be reported to Sentry.

    sentry_sdk.init(
        integrations=[
            BottleIntegration(
                failed_request_status_codes={403, *range(500, 600)},
            )
        ]
    )

    Examples of valid failed_request_status_codes:

    • {500} will only send events on HTTP 500.
    • {400, *range(500, 600)} will send events on HTTP 400 as well as the 5xx range.
    • {500, 503} will send events on HTTP 500 and 503.
    • set() (the empty set) will not send events for any HTTP status code.

    The default is {*range(500, 600)}, meaning that all 5xx status codes are reported to Sentry.

  • Bottle: Delete never-reached code (#​3605) by @​szokeasaurusrex

  • Redis: Remove flaky test (#​3626) by @​sentrivana

  • Django: Improve getting psycopg3 connection info (#​3580) by @​nijel

  • Django: Add SpotlightMiddleware when Spotlight is enabled (#​3600) by @​BYK

  • Django: Open relevant error when SpotlightMiddleware is on (#​3614) by @​BYK

  • Django: Support http_methods_to_capture in ASGI Django (#​3607) by @​sentrivana

    ASGI Django now also supports the http_methods_to_capture integration option. This is a configurable tuple of HTTP method verbs that should create a transaction in Sentry. The default is ("CONNECT", "DELETE", "GET", "PATCH", "POST", "PUT", "TRACE",). OPTIONS and HEAD are not included by default.

    Here's how to use it:

    sentry_sdk.init(
        integrations=[
            DjangoIntegration(
                http_methods_to_capture=("GET", "POST"),
            ),
        ],
    )
Miscellaneous

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, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

socket-security bot commented Oct 8, 2024

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
pypi/[email protected] 🔁 pypi/[email protected] None +2 613 kB

View full report↗︎

Copy link

coderabbitai bot commented Oct 8, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

codecov bot commented Oct 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 46.92%. Comparing base (5a8df13) to head (7214d17).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #49   +/-   ##
=======================================
  Coverage   46.92%   46.92%           
=======================================
  Files           6        6           
  Lines         130      130           
=======================================
  Hits           61       61           
  Misses         69       69           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 0bc1c85 to d01d980 Compare October 17, 2024 09:28
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.16.0 chore(deps): update dependency sentry-sdk to v2.17.0 Oct 17, 2024
@renovate renovate bot changed the title chore(deps): update dependency sentry-sdk to v2.17.0 fix(deps): update dependency sentry-sdk to v2.17.0 Oct 28, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from d01d980 to 12317ef Compare November 4, 2024 15:40
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.17.0 fix(deps): update dependency sentry-sdk to v2.18.0 Nov 4, 2024
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.18.0 fix(deps): update dependency sentry-sdk to v2.19.0 Nov 21, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 12317ef to 3646162 Compare November 21, 2024 17:07
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.19.0 fix(deps): update dependency sentry-sdk to v2.19.1 Dec 5, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 3646162 to 69179a8 Compare December 5, 2024 15:32
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.19.1 fix(deps): update dependency sentry-sdk to v2.19.2 Dec 6, 2024
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 69179a8 to dd7c958 Compare December 6, 2024 10:12
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.19.2 fix(deps): update dependency sentry-sdk to v2.20.0 Jan 14, 2025
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from dd7c958 to 1339586 Compare January 14, 2025 15:30
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.20.0 fix(deps): update dependency sentry-sdk to v2.21.0 Feb 12, 2025
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 1339586 to 72369e6 Compare February 12, 2025 12:05
@renovate renovate bot changed the title fix(deps): update dependency sentry-sdk to v2.21.0 fix(deps): update dependency sentry-sdk to v2.22.0 Feb 17, 2025
@renovate renovate bot force-pushed the renovate/sentry-sdk-2.x branch from 72369e6 to 7214d17 Compare February 17, 2025 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants