Repository navigation
Upgrade pywb to 2.11.0 and Werkzeug to 3.1.9 - #902
Open
santicomp2014 wants to merge 1 commit into
Open
santicomp2014 wants to merge 1 commit into
santicomp2014 wants to merge 1 commit into
Conversation
Werkzeug 3.1.9 fixes GHSA-g6x2-hccm-hh4m (safe_join() allows Windows special device names). pywb 2.10.1 pins werkzeug==3.1.7 exactly, so Werkzeug cannot move without pywb. pywb 2.11.0 replaces that pin with werkzeug>=2.3.5. Recompiled with pip-compile on the pip the repo pins (26.3), upgrading only these two packages. Nothing else changes in requirements/*.txt. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This branch has not been deployed
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.
Closes the 11 open Werkzeug Dependabot alerts in this repo (GHSA-g6x2-hccm-hh4m, fixed in Werkzeug 3.1.9).
Why pywb has to move too
pywb 2.10.1 pins
werkzeug==3.1.7exactly, so Werkzeug cannot be upgraded on its own. pywb 2.11.0 (released 2026-11-02) replaces that pin withwerkzeug>=2.3.5.What changes
pywb2.10.1 to 2.11.0werkzeug3.1.7 to 3.1.9Nothing else changes in
requirements/*.txt. The files were recompiled withpip-compileon the pip version this repo pins (26.3), upgrading only these two packages.What pywb 2.11.0 brings
This is a minor release of the library this service is built on, not only a pin change. From its release notes:
Sec-Fetch-Dest: document.Refreshheader is rewritten, and immediate self-refreshes are skipped.live_url_filterconfig option (off unless configured).sixis no longer a dependency of pywb, and thewebassetspin is relaxed (we stay on 2.0).pywb 2.11.0 still requires
pyOpenSSL<26.2, so thecryptographycap does not change.Testing
lint,checkformatting,tests,coverageandfunctestsall pass.requirements/tests.txtandrequirements/functests.txtinstalled (pywb 2.11.0, Werkzeug 3.1.9 confirmed): 510 unit tests and 29 functional tests pass.The tests cover our patches to pywb (
viahtml/patch.py, the hooks). They do not exercise real sites, and this release changes how frames andRefreshheaders are proxied, so it is worth a look on staging before production.🤖 Generated with Claude Code