build(deps): bump urllib3 from 2.6.3 to 2.7.0 in /tools/gmail/oauth-draft#130
Closed
dependabot[bot] wants to merge 1 commit into
Closed
build(deps): bump urllib3 from 2.6.3 to 2.7.0 in /tools/gmail/oauth-draft#130dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [urllib3](https://github.com/urllib3/urllib3) from 2.6.3 to 2.7.0. - [Release notes](https://github.com/urllib3/urllib3/releases) - [Changelog](https://github.com/urllib3/urllib3/blob/main/CHANGES.rst) - [Commits](urllib3/urllib3@2.6.3...2.7.0) --- updated-dependencies: - dependency-name: urllib3 dependency-version: 2.7.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Member
|
Closing this — urllib3 2.7.0 was released 2026-05-07 and the project's lockfile carries a 7-day cooldown ( Dependabot's solver appears to have ignored the cooldown and forced 2.7.0, which triggered a broken resolution cascade: Dependabot will reopen this once 2.7.0 ages past the cooldown window (or you can rebase the PR after 2026-05-14 and the resolver should produce a clean diff). |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/uv/tools/gmail/oauth-draft/urllib3-2.7.0
branch
potiuk
added a commit
to potiuk/magpie
that referenced
this pull request
May 24, 2026
The github-actions and pre-commit ecosystem blocks in
.github/dependabot.yml carried `semver-{major,minor,patch}-days`
cooldown keys, which those ecosystems do not accept. Dependabot
rejected both blocks outright with:
The property '#/updates/0/cooldown/semver-major-days' is not
supported for the package ecosystem 'github-actions'.
The property '#/updates/1/cooldown/semver-major-days' is not
supported for the package ecosystem 'pre-commit'.
...
which is why neither ecosystem produced a single PR in the four
weeks since adoption on 2026-04-29 (the uv blocks were unaffected
and ran normally — see apache#130, apache#233). Strip the unsupported keys and
keep `default-days: 7` for the 7-day settle window.
Apply the bumps that would have landed already had dependabot been
running, all past the 7-day cooldown:
actions/cache v4.2.2 -> v5.0.5
github/codeql-action v4.35.2 -> v4.35.5
zizmorcore/zizmor-action v0.5.2 -> v0.5.6
astral-sh/setup-uv v7.3.0 -> v8.1.0
actions/cache@v5 needs runner >= 2.327.1 (Node 24), which the
GitHub-hosted runners we target already satisfy. setup-uv@v8 is a
major bump; CI on this commit is the smoke test.
ASF allowlist: setup-uv@08807647 and zizmor-action@5f14fd08 are
already on approved_patterns.yml. actions/cache and
github/codeql-action are exempt — `actions` and `github` are in
TRUSTED_OWNERS in apache/infrastructure-actions/allowlist-check/
check_asf_allowlist.py.
Generated-by: Claude Code (Opus 4.7)
potiuk
added a commit
that referenced
this pull request
May 24, 2026
…mpl (#257) * pr-management-stats: require full engagement schema + add reference impl Fixes three correctness issues in pr-management-stats that cause severe under-counting of engagement and over-counting of untriaged PRs: 1. `fetch.md` previously said "no statusCheckRollup / mergeable / reviewThreads" — claiming none were needed for stats. This is wrong for `reviewThreads`, `latestReviews`, and `timelineItems`: the `is_engaged` predicate in classify.md explicitly counts maintainer line-level review comments, submitted reviews, and label/draft timeline events as engagement. Omitting those fields means a maintainer who only left a line-level review comment is treated as "no engagement" and the PR is misclassified as untriaged. On a ~530-PR queue this inflates the untriaged count ~10× (observed: 225 → 24, then 24 → 2 with full schema + reviewThreads added). 2. `SKILL.md` had no explicit no-skip rule for the 11 dashboard panels. Agents under context pressure were observed simplifying away the line charts, CODEOWNERS table, and triager-activity table. New Golden rule 8 requires all sections to render; missing-data stubs are allowed but silent omission is not. 3. New Golden rule 9 documents the FULL engagement schema explicitly so agents don't trim the query "to save complexity points". Also adds: - `tools/pr-management-stats/reference.py` — canonical reference implementation of the fetch + classify contract. Encodes the full engagement schema and serves as the single source of truth agents can read from. - `tools/pr-management-stats/README.md` — describes how the agent invokes the reference + the anti-skip contract. - Updated GraphQL template in fetch.md to include the engagement fields, with batch size dropped from 50 to 30 to absorb the ~11-point complexity increase per page. * chore(ci): fix dependabot cooldown schema and bump pinned actions The github-actions and pre-commit ecosystem blocks in .github/dependabot.yml carried `semver-{major,minor,patch}-days` cooldown keys, which those ecosystems do not accept. Dependabot rejected both blocks outright with: The property '#/updates/0/cooldown/semver-major-days' is not supported for the package ecosystem 'github-actions'. The property '#/updates/1/cooldown/semver-major-days' is not supported for the package ecosystem 'pre-commit'. ... which is why neither ecosystem produced a single PR in the four weeks since adoption on 2026-04-29 (the uv blocks were unaffected and ran normally — see #130, #233). Strip the unsupported keys and keep `default-days: 7` for the 7-day settle window. Apply the bumps that would have landed already had dependabot been running, all past the 7-day cooldown: actions/cache v4.2.2 -> v5.0.5 github/codeql-action v4.35.2 -> v4.35.5 zizmorcore/zizmor-action v0.5.2 -> v0.5.6 astral-sh/setup-uv v7.3.0 -> v8.1.0 actions/cache@v5 needs runner >= 2.327.1 (Node 24), which the GitHub-hosted runners we target already satisfy. setup-uv@v8 is a major bump; CI on this commit is the smoke test. ASF allowlist: setup-uv@08807647 and zizmor-action@5f14fd08 are already on approved_patterns.yml. actions/cache and github/codeql-action are exempt — `actions` and `github` are in TRUSTED_OWNERS in apache/infrastructure-actions/allowlist-check/ check_asf_allowlist.py. Generated-by: Claude Code (Opus 4.7) * fix(pr-management-stats): use placeholders in fetch.md + README example `check-placeholders` pre-commit hook (and skill-validator pytest) rejected hardcoded `apache/airflow` references in: .claude/skills/pr-management-stats/fetch.md:414 tools/pr-management-stats/README.md:39 Replace with `<upstream>` (the skill's existing placeholder for the project repo, used on fetch.md lines 171, 178, 185, 193, 203, 223, 238, 348). Also swap `potiuk` for `<maintainer-handle>` in the README invocation so the example matches the placeholder convention end-to-end. doctoc TOC added by pre-commit on first README edit. Generated-by: Claude Code (Opus 4.7) * fix(pr-management-stats): typos in reference.py flagged by `typos` hook prek's `typos` hook caught: - `invokable` -> `invocable` (docstring, line 23) - `thr` -> `thread` (loop variable in the reviewThreads walk, lines 257-258) Pure rename + spelling fix; no behaviour change. Generated-by: Claude Code (Opus 4.7)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps urllib3 from 2.6.3 to 2.7.0.
Release notes
Sourced from urllib3's releases.
Changelog
Sourced from urllib3's changelog.
... (truncated)
Commits
9a950b9Release 2.7.05ec0de4Merge commit from fork2bdcc44Merge commit from forkf45b0dfFix a misleading example forProxyManager(#4970)577193cSwitch to nightly PyPy3.11 in CI for now (#4984)e90af45Avoid infinite loop inHTTPResponse.read_chunkedwhenamt=0(#4974)67ed74fBump dev dependencies (#4972)3abd481Upgrade mypy to version 1.20.2 (#4978)2b8725dDrop support for EOL PyPy3.10 (#4979)2944b2aUpgradesetup-chromeandsetup-firefoxto fix warnings (#4973)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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)You can disable automated security fix PRs for this repo from the Security Alerts page.