Repository navigation
chore(deps): bump pyjwt from 2.13.0 to 2.14.0 in /envs/wildfire_env - #1275
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [pyjwt](https://github.com/jpadilla/pyjwt) from 2.13.0 to 2.14.0. - [Release notes](https://github.com/jpadilla/pyjwt/releases) - [Changelog](https://github.com/jpadilla/pyjwt/blob/master/CHANGELOG.rst) - [Commits](jpadilla/pyjwt@2.13.0...2.14.0) --- updated-dependencies: - dependency-name: pyjwt dependency-version: 2.14.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
Contributor
There was a problem hiding this comment.
Alignment Review Report
Automated Checks
- Lint: FAIL (pre-existing, unrelated to this diff) —
usort/ruff format --checkflag 56 files acrosssrc/andenvs/, none of which are touched by this PR. This PR only editsenvs/wildfire_env/uv.lock. - Debug code: FOUND (pre-existing, unrelated to this diff) —
print()/TODO occurrences exist insrc/openenv/cli/commands/{harbor,serve,collect}.pyand a couple of other files, none touched by this PR.
Open RFCs Context
RFCs currently in Draft/In Review: 000, 001, 002, 003, 005, 008, 011, 012. None of these govern dependency/lockfile management, and this change doesn't touch any code path they cover.
Tier 1: Fixes Required
- None. The diff is a single transitive-dependency bump (
pyjwt2.13.0 → 2.14.0, pulled in viapyjwt[crypto]) confined entirely toenvs/wildfire_env/uv.lock(hash/URL/version fields only). No source files changed.
Tier 2: Alignment Discussion
Principle Conflicts
None identified. No API, client/server boundary, reward, or container-isolation code is touched.
RFC Conflicts
None identified. No open RFC covers dependency pinning for wildfire_env.
Summary
- 0 mechanical issues introduced by this change (pre-existing repo-wide lint/debug findings are out of scope for this diff)
- 0 alignment points for human review
- 0 RFC conflicts to discuss
This is a routine, low-risk Dependabot lockfile bump with no code or behavioral changes. Safe to merge.
Sent by Cursor Automation: Pre-review
Contributor
Author
|
Superseded by #1283. |
dependabot
Bot
deleted the
dependabot/uv/envs/wildfire_env/pyjwt-2.14.0
branch
September 30, 2026 15:55
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
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 pyjwt from 2.13.0 to 2.14.0.
Release notes
Sourced from pyjwt's releases.
Changelog
Sourced from pyjwt's changelog.