Bump sentry-sdk from 1.11.1 to 1.12.1 #525
Conversation
Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 1.11.1 to 1.12.1. - [Release notes](https://github.com/getsentry/sentry-python/releases) - [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md) - [Commits](getsentry/sentry-python@1.11.1...1.12.1) --- updated-dependencies: - dependency-name: sentry-sdk dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Codecov Report
@@ Coverage Diff @@
## main #525 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 18 18
Lines 2034 2034
Branches 231 231
=========================================
Hits 2034 2034
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
It's pretty noisy to have dependabot open 6 PRs at once, each just changing one dependency (even though it perhaps is more atomic). It also means the new dependencies aren't all tested together, as opposed to individually (which allows detecting dependency-specific issues, but does not actually test the final composed product of all of the updates until the final PR is merged). Is it possible to have dependabot submit one PR with all the updates at the designated interval? It wasn't clear from skimming the docs whether that is possible. |
Unfortunately not. dependabot/dependabot-core#1190 is the number-1 upvoted dependabot issue; you're not the only one to have wanted this. |
|
Ah, I see, thanks. I also realized something more important when I wondered how I got subscribed to all notifications in this repo in the first place...apparently (perhaps due to python/core-workflow#460 ) I have Write permissions here, which subscribes you automatically, and it seems that none of the branch protection steps were implemented, so I (and I assume any other triager) can merge PRs, push branches, etc. willy nilly. That should be fixed by an admin here...maybe @Mariatta can help? I've listed the steps needed on that issue. |
|
I don't have admin privs on the bedevere repo. Perhaps @brettcannon ? |
Dependabot (sometimes? always?) rebases PRs after others are merged, so they do end up getting tested together. For example, see the force pushes to #524.
No, but I use Renovate on my projects, which can be configured to create a single, grouped PR. For example: hugovk/pypistats#368 / https://github.com/hugovk/pypistats/blob/main/.github/renovate.json |
IIUC she rebases when a previous change (e.g. to Having multiple PRs is good because sometimes you don't want to merge them all (e.g. in case one of the dependencies has breaking changes or issues). |
Nope, I'm not an admin. |
|
Okay, thanks. Then I guess @python/organization-owners ? It would have had to be an admin to make the change in the first place... |
I think you can also email admin at python for help. |
Bumps sentry-sdk from 1.11.1 to 1.12.1.
Release notes
Sourced from sentry-sdk's releases.
Changelog
Sourced from sentry-sdk's changelog.
Commits
ab1496frelease: 1.12.16959941Link errors to OTel spans (#1787)561cd4bMerge branch 'release/1.12.0'abfdce8Updated changelog0a02915release: 1.12.0d0eed0eBasic OTel support (#1772)eb0db0aTox Cleanup (#1749)dd26fbefix(ci): Fix Github action checks (#1780)b1290c6feat(profiling): Introduce active thread id on scope (#1764)46697ddAdd instrumenter config to switch between Otel and Sentry instrumentation. (#...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)