Skip to content

chore(deps): weekly uv.lock refresh - #827

Merged
Seth Fitzsimmons (sethfitz) merged 1 commit into
mainfrom
uv-lock-refresh
Nov 17, 2026
Merged

Seth Fitzsimmons (sethfitz) merged 1 commit into
mainfrom
uv-lock-refresh

Conversation

@overture-pull-requester

Copy link
Copy Markdown
Contributor

Automated uv lock --upgrade at the workspace root. Re-resolves every dependency, direct and transitive, to the newest version pyproject.toml allows. pyproject.toml files are unchanged.

Package From To Notes
coverage 7.16.2, 7.17.0 7.16.2, 7.17.2 PyPI
dnspython 2.8.0, 2.9.0 2.8.0, 2.9.2 PyPI
jsonpath-ng 1.8.0, 1.14.0 1.8.0, 1.16.0 changelog
mypy-extensions 1.1.0 1.2.0 PyPI
pydantic 2.14.1 2.14.2 changelog
pydantic-core 2.50.1 2.50.2 PyPI
pydoclint 0.11.1 0.12.0 PyPI
pyspark 4.2.1 4.2.1, 4.3.0 PyPI
pytest-testmon 2.2.0 2.2.0, 2.3.0 PyPI
types-pyyaml 6.0.12.20260906 6.0.12.20261103 changelog
types-shapely 2.1.0.20260728 2.1.0.20261030 changelog
typing-inspection 0.4.4 0.4.5 changelog

@overture-pull-requester overture-pull-requester Bot added automation 🦾 Change/enhance automation of a process bot labels Nov 12, 2026
@github-actions

Copy link
Copy Markdown

⚠️ vnext compatibility conflict detected

If this PR merges to main, vnext cannot be cleanly rebased on top.
Your changes conflict with something already on vnext.

Conflicting files:

uv.lock

How to fix:

Do not rebase your branch onto vnext — that would pull unreleased breaking
changes into main. Instead:

  1. See exactly what vnext changes in the conflicting file(s):
git fetch origin
git diff origin/main...origin/vnext -- uv.lock
  1. Open each conflicting file in your editor. The diff above shows what vnext adds
    or changes there — adjust your edits so they no longer overlap with those lines.
  2. Commit the adjustment and push:
git add uv.lock
git commit -m "fix: resolve vnext compatibility"
git push origin uv-lock-refresh

After pushing, this check will re-run automatically.

@github-actions

github-actions Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

🗺️ Schema reference docs preview is live!

🌍 Preview https://staging.overturemaps.org/schema/pr/827/schema/index.html
🕐 Updated Nov 13, 2026 18:07 UTC
📝 Commit 96fea64
🔧 env SCHEMA_PREVIEW true

Note

♻️ This preview updates automatically with each push to this PR.

@sethfitz

Copy link
Copy Markdown
Collaborator

John McCall (@lowlydba) #829 attempts to fix the automation that's causing this to fail CI.

@github-actions

Copy link
Copy Markdown

⚠️ vnext compatibility conflict detected

If this PR merges to main, vnext cannot be cleanly rebased on top.
Your changes conflict with something already on vnext.

Conflicting files:

uv.lock

How to fix:

Do not rebase your branch onto vnext — that would pull unreleased breaking
changes into main. Instead:

  1. See exactly what vnext changes in the conflicting file(s):
git fetch origin
git diff origin/main...origin/vnext -- uv.lock
  1. Open each conflicting file in your editor. The diff above shows what vnext adds
    or changes there — adjust your edits so they no longer overlap with those lines.
  2. Commit the adjustment and push:
git add uv.lock
git commit -m "fix: resolve vnext compatibility"
git push origin uv-lock-refresh

After pushing, this check will re-run automatically.

Signed-off-by: overture-pull-requester[bot] <overture-pull-requester[bot]@users.noreply.github.com>
@sethfitz Seth Fitzsimmons (sethfitz) changed the title [CHORE](deps) weekly uv.lock refresh chore(deps) weekly uv.lock refresh Nov 13, 2026
@sethfitz Seth Fitzsimmons (sethfitz) changed the title chore(deps) weekly uv.lock refresh chore(deps): weekly uv.lock refresh Nov 13, 2026
@sethfitz

Copy link
Copy Markdown
Collaborator

Woohoo! #829 (and #830) worked.

@sethfitz
Seth Fitzsimmons (sethfitz) merged commit b9aa177 into main Nov 17, 2026
41 of 43 checks passed
@sethfitz
Seth Fitzsimmons (sethfitz) deleted the uv-lock-refresh branch November 17, 2026 05:18

This branch was successfully deployed

1 active deployment
staging — 96fea644 Deployed Nov 17, 2026 by sethfitz via Cleanup #195
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation 🦾 Change/enhance automation of a process bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants