build(deps): update dependency responses to ~=0.26.1 (hotfix/6.2)
Metadata
Current evaluation
Closed dependency update request for the responses package to version 0.26.1. The automated pull request was not merged and was likely ignored or superseded.
Suggested action: —
No scores available.
Issue body
This PR contains the following updates:
| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [responses](https://redirect.github.com/getsentry/responses) ([changelog](https://redirect.github.com/getsentry/responses/blob/master/CHANGES)) | `~=0.25.0` → `~=0.26.1` |  |  |
---
### Release Notes
<details>
<summary>getsentry/responses (responses)</summary>
### [`v0.26.1`](https://redirect.github.com/getsentry/responses/blob/HEAD/CHANGES#0261)
[Compare Source](https://redirect.github.com/getsentry/responses/compare/0.26.0...0.26.1)
- Added Spanish translation of the README (`README.es.rst`)
- When both `content_type` and `headers['content-type']` are in a response mock file,
`content_type` is now used.
- Added strict\_match to urlencoded\_params\_matcher, enabling partial request parameter
matching.
### [`v0.26.0`](https://redirect.github.com/getsentry/responses/blob/HEAD/CHANGES#0260)
[Compare Source](https://redirect.github.com/getsentry/responses/compare/0.25.8...0.26.0)
- When using `assert_all_requests_are_fired=True`, assertions about
unfired requests are now raised even when an exception occurs in the context manager or
decorated function. Previously, these assertions were suppressed when exceptions occurred.
This new behavior provides valuable debugging context about which mocked requests were
or weren't called.
- Consider the `Retry-After` header when handling retries
</details>
---
### Configuration
📅 **Schedule**: (in timezone Etc/UTC)
- Branch creation
- "every weekend"
- 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.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/canonical/craft-application).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xOTQuMCIsInVwZGF0ZWRJblZlciI6IjQzLjE5NC4wIiwidGFyZ2V0QnJhbmNoIjoiaG90Zml4LzYuMiIsImxhYmVscyI6WyJQUjogRGVwZW5kZW5jaWVzIl19-->
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed dependency update request for the responses package to version 0.26.1. The automated pull request was not merged and was likely ignored or superseded. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
60
Complexity:
5
Confidence:
85
|
needs review | Updates the responses Python dependency from 0.25.0 to 0.26.1 on the hotfix/6.2 branch. Generated by Renovate with automerge disabled, it is currently awaiting manual maintainer approval. No comments or CI feedback present. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1080 build(deps): update dependency responses to ~=0.26.1 (hotfix/5.11) | craft-application | closed | Closed without merging due to failing CI checks, including OSV-scanner, test failures, and lint errors. The responses dependency update to 0.26.1 was abandoned. | |
| #1020 build(deps): update dependency responses to ~=0.26.0 (main) | craft-application | merged | Merged automated dependency update for responses from 0.25.0 to 0.26.0. Approved by two reviewers with all CI checks passing. Changes update version constraints and configuration across two files. | |
| #5066 build(deps): update dependency requests to v2.32.2 [security] (hotfix/8.3) | snapcraft | closed | Closed without merging. The requests security update to v2.32.2 was abandoned due to inactivity, with no reviewer comments or CI checks. Likely superseded by a newer dependency update. | |
| #6126 build(deps): update dependency requests to v2.33.0 [security] (hotfix/8.14) - autoclosed | snapcraft | closed | Automated dependency update to requests v2.33.0 was abandoned and autoclosed without merging due to failing CI checks and unreviewed status. | |
| #1223 build(deps): update bugfixes (hotfix/1.5) | rockcraft | closed | Closed unmerged due to failing CI checks across multiple test suites and linters. Dependency updates were not applied. The automated bot will recreate the request. | |
| #5550 build(deps): update dependency requests to v2.32.4 [security] (hotfix/7.5) - autoclosed | snapcraft | closed | Automated dependency update to requests v2.32.4 for CVE-2024-47081 was autoclosed without merging. The security patch was abandoned and not applied to the repository. | |
| #338 build(deps): update bugfixes (hotfix/3.2) | craft-store | closed | Dependency updates were closed as stale. Failing OSV-scanner and minimum dependency checks led a maintainer to mark the branch stale, resulting in the pull request being abandoned without merging. | |
| #1921 build(deps): update dependency requests to v2.32.2 [security] (hotfix/2.7) - autoclosed | charmcraft | closed | Renovate bot pull request updating requests to v2.32.2 to address CVE-2024-35195 was autoclosed. The dependency update was not merged and remains abandoned, likely due to branch deletion or being superseded by another resolution. | |
| #1922 build(deps): update dependency requests to v2.32.2 [security] (hotfix/3.2) - autoclosed | charmcraft | closed | Automated update to requests v2.32.2 for CVE-2024-35195 on the hotfix/3.2 branch. The pull request was autoclosed without review or merge, indicating it was abandoned or superseded. | |
| #1519 build(deps): update dependency requests to v2.33.0 [security] (hotfix/2.7) | craft-parts | closed | Updated requests to v2.33.0 to patch CVE-2026-25645. Closed without merging, likely due to failing CI checks or abandonment. No reviewer comments were recorded. |