Both are the watch's own setting, same as the single watch GET. "Pause all" and
"mute all" stay separate (all_paused/all_muted in /systeminfo), folding them in
would be wrong info and a client writing the values back would pause every watch.
Spec: SearchResult now matches the real response (no "watches" wrapper).
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Fix two races behind flaky tests: favicon cache and a new monitor queued twice
- Favicon: get_favicon_filename() could glob before a save and store its "no favicon" after the save cleared
the cache, leaving the icon missing until the next save. The lookup and the clearing now share a lock.
test_favicon_url_change also lets the new monitor's first check finish before saving a favicon.
- Scheduler: its queued/running lists are from the start of a pass, so a monitor a worker had just taken off
the queue (not claimed yet) looked idle and was queued again, and that copy was re-queued until the first
check finished, so it ran twice (test_fallback_fetchers_chain_in_priority_order saw 2 calls). The ticker now
re-checks live before queueing and stamps scheduled_at; a worker drops a scheduled item when the monitor
was checked since then.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Bump licence
* Fix two more races from this PR's CI: a new watch's first check before the test (or its config) is ready
- tests/util.py wait_for_all_checks(client): an import or API create doesn't queue the watch, the scheduler picks
it up on its next pass, so the queue could be empty (and the wait return) before the first check started; the
test then changed the page under it. test_nonrenderable_pages failed this way: the first check fetched the
"no text" page, so no first snapshot. It now also waits (5s at most) until every unpaused watch was checked.
- api/operations create_watch: the processor config was saved after add_watch(), so the scheduler could check the
new watch with the processor's defaults first (test_example_wordcounter_processor_plugin counted 7 words, not
5). With processor config it's added paused until the config is saved.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Tests - queue UI: keep workers stopped through the scheduler's health check, and restore them after
_quiesce() stops every worker, but the scheduler's worker health check (every 60s, even while paused) restarts
them up to FETCH_WORKERS / the workers setting; when it fired during a test they took the sentinel and the test
failed with "Could not get queue to a quiescent state". It now expects 0 workers for the test (FETCH_WORKERS and
the setting, via monkeypatch). The workers were also never put back, so the next test on that pytest worker ran
with none until the health check: an autouse fixture now restores the count they had before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Plugins - select_fetch_backend and recheck_seconds_override hooks, with a fallback fetcher example plugin
select_fetch_backend lets a plugin pick another fetcher for one check: before it, or as a single
immediate retry after the fetch failed (e.g. the site answered 403). The watch's settings are never
changed. recheck_seconds_override gives a plugin the last word on the recheck time, after system,
group and watch, used by the scheduler and the overdue count.
The fallback fetcher example registers a fetcher for a generic scraping API, retries blocked checks
through it, then keeps the watch under its control for a while with a minimum recheck time and a
note in the watch list. Plugin API 0.6.0, which also exports Non200ErrorCodeReceived.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Plugins - chain fallback fetchers by priority, plus a daily limit, stats page and recheck widget in the example
select_fetch_backend now collects every plugin's offer (a name, or {'backend', 'priority'}) and core
tries them lowest priority first, skipping fetchers already tried in this check (new 'tried' argument),
up to FETCH_FALLBACK_MAX_ATTEMPTS retries (default 3). The last error is shown when they all fail.
The fallback fetcher example:
- a Priority setting, and it doesn't offer itself when over its daily limit, so the next one goes
- 'Most successful calls in 24 hours', counted in its own {datastore}/<plugin>-state.json
- takes a watch over only once a fallback fetch through it worked
- the minimum recheck time uses core's TimeBetweenCheckForm widget, fixed read-only by
EXAMPLE_FETCHER_HELLOWORLD_TIME_BETWEEN_RECHECK_MINIMUM_SECONDS when set
- a 'Fetch stats' page with a sidebar icon
Core: plugin_api exports TimeBetweenCheckForm and time_between_check_to_seconds (now also used by
Watch.threshold_seconds), and plugin settings tabs show each field's description.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* MCP server at /mcp, plus GET /api/v1/changes, so AI assistants (Claude, ChatGPT, Cursor...) can use changedetection.io
/mcp - a small hand-written implementation of MCP's Streamable HTTP transport in its stateless form: one POST
per JSON-RPC message, plain JSON back, no SSE stream and no sessions, no new dependency. The app is a single
process, so every MCP call is a normal short request and every tool is bounded.
- 21 tools: read (list_watches, get_watch with the latest change, list_tags, get_changes, get_diff, get_snapshot,
get_system_info, list_notifications), write (create_watch, import_watches, update_watch, recheck_watches,
add_tags/remove_tags by name, create_tag, update_tag, add_notification) and destructive (delete_watch, never
'all', clear_history, delete_tag, remove_notification), with tool annotations. /mcp?readonly=1 serves the
read-only ones only.
- A 'watch' can be its uuid or part of its title/URL; ambiguous names return the candidates.
- Arguments are validated against each tool's schema (unknown keys, types, ranges, all errors at once, as a
tool error). Watch fields take their limits from the API spec.
- Auth is the REST API key (x-api-key or Authorization: Bearer), also required whenever the UI is password
protected; Origin is checked against DNS rebinding. Page text in results is marked as untrusted.
- Rechecks are only queued, get_changes has a time budget and yields between watches.
GET /api/v1/changes - every change across a group of watches between two dates as unified diffs, net_change
(default) or each, with totals; shared with the MCP get_changes tool (changes_report.py).
api/operations.py - watch create/update and tag create/update/delete moved out of the REST handlers so REST and
MCP validate and answer the same way, now also checking values against the API spec's CreateWatch/UpdateWatch
schemas. /api/v1/systeminfo also returns fetch_workers and checking_now (which watches are being checked, for
how long).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Spec validation follows the merged spec cache, a plugin processor registered later wasn't accepted
The validator and the MCP watch field schemas were cached on their own, so after a plugin processor was
registered (the merged API spec cache cleared, as test_example_processor_plugin does) they still held the old
spec: "processor: must be one of image_ssim_diff, restock_diff, text_json_diff" for word_counter. Each now keeps
the spec object it was built from and is rebuilt when that changes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* MCP - "MCP Server" tab at /settings/ai/mcp, its own access token, DISABLE_MCP
The AI settings are two pages with tabs: /settings/ai/llm (AI / LLM, the default) and /settings/ai/mcp
(MCP Server). Each tab is its own route, not an #anchor, so each page's form stands alone. /settings/ai and
the previous /settings/llm redirect to /settings/ai/llm.
The MCP Server tab explains what MCP is and shows the server address (the Base URL setting when set,
otherwise built from the request, X-Forwarded-* included), the MCP access token with click to copy and
"Regenerate MCP token", the Claude Code command, the read-only address, configs for Cursor, VS Code and
Claude Desktop, and what an assistant can and can't do.
- MCP has its own token, settings.application.mcp_access_token, separate from the REST API key and always
required (Authorization: Bearer or x-api-key). It's created at startup for any datastore without one.
- /mcp is off (not registered, or 404 when switched later) with DISABLE_MCP=true or LLM_FEATURES_DISABLED.
- A debug log line per tool call, with how long it took.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Adding text and infographics
* MCP - Read-only mode switch, mcp-types for protocol versions and request validation, AI settings as a /settings tab
- "Read-only" checkbox on the MCP Server tab (settings.application.mcp_read_only): write tools are hidden from
tools/list, initialize instructions say the server is read-only, and a write tool called anyway (e.g. from a
cached tool list) gets a tool error the assistant can pass on. ?readonly=1 now gets the same readable error
instead of "Unknown tool".
- Use the official SDK's wire types (`mcp-types`, MIT, needs only pydantic) instead of the full ASGI `mcp` SDK:
protocol versions come from mcp_types.version, requests are validated against the negotiated version's schema,
and an unsupported MCP-Protocol-Version header is a 400. It costs ~15MB on import, so it is only imported on
the first authenticated /mcp request (test_mcp_types_imported_lazily guards that).
- MCP page is one form with the same Save button at the bottom as the AI / LLM page; "Regenerate MCP token"
posts via formaction.
- The AI link moves from the left sidebar to an "AI / LLM / MCP" tab on /settings. The tab row is a shared
settings_tabs() macro, so the AI pages show it with that tab active and the other tabs link back to
/settings#<tab>. AI / LLM | MCP Server becomes a segmented switch inside the box.
- test_ai_settings_csrf: with CSRF switched back on, every AI settings POST without a token is refused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* UI tweaks
* rebuild translations
* bump licence doc
* MCP - On/off switch, named access tokens with per-token permissions, notification tools, processor plugin tools
- Switch at the top of the MCP Server tab, off by default, covering the MCP (and future OAuth) endpoints; every
sub-tab can be set up while it's off
- Endpoint versioned as /mcp/v1
- Named access tokens (one per assistant), stored SHA-256 hashed and shown once, each with its own
None / Read / Write grid for monitors, groups, notifications and system info; add / edit overlay saved with ajax
(X-CSRFToken), revoke with the confirm dialog, "last used" and client name. Replaces the single token and the
server-wide read-only switch (never released)
- notification_* arguments of update_watch / update_tag / create_tag need Notifications: write
- list_notifications shows format, title, body and muted; notification_services (from Apprise details());
add_notification from service + tokens
- register_mcp_tools pluggy hook for processor plugins, with the built-in restock_status / restock_set_rules
- get_watch shows processor fields the same way as the REST API
- MCP Server tab rebuilt on the vertical sub-tabs: Overview, Connect, Access tokens, OAuth connections
- AI / LLM | MCP Server switch readable on the white box, Regenerate API key asks for confirmation
- Translations for all languages
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* MCP - get_snapshot unfiltered (whole page from the saved HTML) and over many monitors, in/out direction on the AI pages
- get_snapshot unfiltered=true: the HTML saved with the snapshot through html_to_text, non-HTML content as it is,
the filtered text (saying so) when no page was kept; logged start/done per monitor
- get_snapshot with 'watches' or a 'tag': paged (limit/offset), per-monitor character cap, time budget, and a
warning when more than 100 monitors match
- AI / LLM | MCP Server switch: outgoing / incoming arrows and a subtitle, teal accent for the MCP page
- Translations
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* MCP settings - one translated string per line, for the fragmented-gettext CI check
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* rebuild translations
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* bump
* AI settings - Load models / Test connection work for a keyless server (Ollama) at an address not saved yet
The credential guard (GHSA-g36r-fm2p-87xm) refused any api_base that differs from the saved one when no api_key
was sent, even with no key saved at all, so trying a local Ollama before Save failed with "api_key is required
when api_base differs from the saved configuration". It now refuses only when a key is saved. The connection
test then sends a placeholder key, so litellm can't fall back to a provider key from the environment.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Licences - regenerate THIRD-PARTY-LICENSES.md (Flask-SocketIO 5.7.1 reports its licence as MIT, python-socketio 5.18.0, WTForms 3.3.2)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Settings sub-tabs - the URL hash selects the tab (/settings/ai/llm#prompts, /settings/ai/mcp#connect), switching tabs updates it
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* MCP Server tab - Get started steps, "add your first token" call to action, floating copy hint
- Overview: "Get started" steps (switch on, add a token, connect) until the server is on and has a token, then the
tokens as blue links; refreshed with every token change, no page reload needed
- Access tokens: an empty list is a blue "Add your first access token" call to action that opens the overlay
- Sub-tabs reordered: Overview, Access tokens, Connect, OAuth; the client configs on Connect are all shown
- Click to copy: "copy" + icon floats over the box (top right of code blocks, right of inline values) instead of
pushing the page down, lingers 2s, the hint itself is clickable; the API key on /settings uses it too
- Translations
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* AI settings - llm-settings.html is one wrapper for both AI pages, including llm-settings_llm.html or llm-settings_mcp.html
The wrapper has the /settings tab row, the AI / LLM | MCP Server switch and the scripts; each page's form is its own
file (mcp-settings.html becomes llm-settings_mcp.html). Translations: locations only.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* MCP settings test - the on/off switch sits under Overview's introduction now
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* rebuild
* AI settings - restore the llm-settings.html wrapper, move "Switch thinking off" into llm-settings_llm.html
The merge of master (#4643) put the whole old single-file llm-settings.html back over the wrapper, so both AI pages
returned 500. The wrapper is back, and #4643's checkbox and its show/hide lines are in the AI / LLM part, where that
form lives now.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* API - systeminfo `overdue_watches` no longer lists paused watches (#4607)
Paused watches aren't supposed to be checked, so they can't be overdue. The same goes for every watch while
"pause all" (all_paused) is on.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Test the overdue rule directly, the live-server test raced the scheduler in CI
Against the live app the scheduler checks an overdue watch straight away, so by the time the test asked
/api/v1/systeminfo the watch had just been checked and wasn't overdue any more. The rule now lives in
overdue_watch_uuids(datastore, now), which the endpoint calls, and a unit test checks it with fixed times
(paused, "pause all", just checked, within the grace period, the system default interval, never checked).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Example plugins - API fetcher and check stats examples, watch list notes hook, update_finalize fix
New hook watch_list_extra_text(watch) (ported from browser-ui): short plain-text notes under each watch
in the watch list, escaped when rendered.
New example plugins, each `pip install .`-able and importing only from plugin_api:
- fetcher/api_fetcher: register_content_fetcher, plugin_settings_tab, fetcher_status_icon, plugin_static_path
- lifecycle/check_stats: update_handler_alter, update_finalize, watch_list_extra_text, ui_edit_stats_extras,
get_html_head_extras, plugin_static_path
- processor/wordcounter: also shows "Found: N words" in the watch list via watch_list_extra_text
Fixes found by the examples:
- update_finalize always got update_handler=None after a successful check (the worker deleted the handler
before the finally block captured it), so update_handler_alter + update_finalize couldn't be paired
- The API rejected plugin fetchers in 'fetch_backend' (hardcoded pattern), now built from installed fetchers
- fetcher_status_icon docstring said it returns HTML, it returns a dict
plugin_api 0.3.0: exports Fetcher and load_plugin_settings.
Tests check each example end to end, including that it's listed under Settings > Info.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Example plugins - Rename the fetcher example to fetcher/example_browser_fetcher
"Example browser fetcher": an extra fetcher that gets pages through its own API. Package
cdio_example_browser_fetcher, fetch method html_example_browser_fetcher.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Example browser fetcher - Return a screenshot (random noise PNG, standard library only)
Shows the screenshot side of a fetcher: supports_screenshots = True and self.screenshot set to PNG bytes,
saved as last-screenshot.png. The test checks it's served as a valid 240x160 PNG.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* API - Add processor_state_{processor_name} to watch GET and list (current restock price/stock)
The current restock/price state (watch['restock']) was hidden from the API, the only way to
see it was parsing the "In Stock: True - Price: 19.99" history snapshot text.
- New pluggy hook get_api_watch_processor_state(watch, processor_name, context), core picks
the response key processor_state_{processor_name} so a plugin can't overwrite other fields
- restock_diff implements it (in_stock, price, currency, last_price)
- processor_state_* is returned on GET /api/v1/watch/{uuid} and on each item of GET /api/v1/watch,
the list items also gain 'processor'
- processor_config_{name} resolution is now generic in core instead of restock-specific code in
api/Watch.py, still single watch GET only (disk read), and only for the watch's own processor
- A processor_state_{name} schema in a processor's api.yaml is merged into Watch as readOnly
- GET -> PUT round trips no longer save processor_config_*_source into the processor config file
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* API - Accept every installed processor (plugins, image_ssim_diff) in the watch 'processor' field
The static spec enum only listed restock_diff and text_json_diff, so a plugin processor (and the
built-in image_ssim_diff) couldn't be set on a watch via the API. The merged spec now fills the
enum from find_processors(). Also corrects the register_builtin_restock_plugins() docstring, it is
only called from main().
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Add example processor plugin (word counter), and mark the processor storage problem
changedetectionio/example_plugins/processor/wordcounter is a working processor plugin to copy:
register_processor, processor.py, api.yaml (processor_config_word_counter / processor_state_word_counter)
and get_api_watch_processor_state. Nothing scans example_plugins/, it is only active when registered.
The new test registers it the same way a pip-installed plugin is, then creates a watch via the API and
checks processor_state_word_counter on the watch GET and list, the GET -> PUT round trip and the snapshot.
Shipped in the sdist via MANIFEST.in.
Processors have no storage of their own for what a check found, update_obj is merged straight into the
watch. Marked with @IMPORTANT-TODO where it shows up, the fix is planned as its own PR for a new release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* plugin_api - Export what a processor plugin needs, example plugin uses only the public API
- plugin_api exports difference_detection_processor, get_resolved_processor_config and html_to_text,
lazily (module __getattr__) so importing plugin_api stays cheap. PLUGIN_API_VERSION 0.1.0 -> 0.2.0
- The word counter example and the restock api_state plugin import only from plugin_api
- Fix: importing plugin_api before anything else in the package was a circular import (plugin_api ->
pluggy_interface -> built-in conditions plugins -> plugin_api.hookimpl). The hookimpl marker now lives
in plugin_api and pluggy_interface imports it from there.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* plugin_api - Declare the lazy exports under TYPE_CHECKING so ruff F822 (and IDEs) see them
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Test - plugin_api cheap-import check runs the fresh interpreter from the package's parent dir
CI runs pytest from inside changedetectionio/, where a new interpreter can't import the package.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* API - `GET /api/v1/watch` add `with_errors=1` filter, `recheck_all=1` no longer rechecks paused watches (#4506)
`recheck_all=1` now rechecks only the watches that were listed (honouring
`tag` and the new `with_errors` filter) and skips paused watches, matching
the UI "Recheck all" behaviour.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* bump docs
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* API - Reject broken Jinja2 in url, link_to_open, body and headers, shared validation with the edit form
The edit form validated Jinja2 templates on save but the API did not, so a broken body or
header template saved through the API only failed at fetch time, on every check.
- New jinja2_custom/validate.py: validate_jinja2_fields() renders each value that matches
JINJA2_MARKER_PATTERN and returns {field: translated error}
- The edit form uses it instead of four copies of the same try/except
- API create and update return 400 naming the field
Translations: messages moved to the new file (msgids unchanged); also translated the header
error for fr/it and fixed the cs/es wording.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* rebuild
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Scheduler+API Bug - if an invalid timezone was set (through edit of watch or API) it could have crashed the scheduler, Added `timezone` to the official API docs
* adding missing files
* Non blocking improvements
* Test fix
* Background thread re-queue
* Nonblockimg improvements, run tasks in background, add warning about CPU cores
* Misc fixes
* No need to add imported items to the check queue, the scheduler will do this #3762
* Tests - Faster recheck/reschedule loop under pytest environment
* More wait time under test
* Bunch up some tests a little
* fix typo
* woops
* If they want to queue one thats already running, thats up to them.
* WIP
* Fixing queue limit size
* Increase max queue size and many CPU performance fixes
Multi-language / Translations Support (#3696)
- Complete internationalization system implemented
- Support for 7 languages: Czech (cs), German (de), French (fr), Italian (it), Korean (ko), Chinese Simplified (zh), Chinese Traditional (zh_TW)
- Language selector with localized flags and theming
- Flash message translations
- Multiple translation fixes and improvements across all languages
- Language setting preserved across redirects
Pluggable Content Fetchers (#3653)
- New architecture for extensible content fetcher system
- Allows custom fetcher implementations
Image / Screenshot Comparison Processor (#3680)
- New processor for visual change detection (disabled for this release)
- Supporting CSS/JS infrastructure added
UI Improvements
Design & Layout
- Auto-generated tag color schemes
- Simplified login form styling
- Removed hard-coded CSS, moved to SCSS variables
- Tag UI cleanup and improvements
- Automatic tab wrapper functionality
- Menu refactoring for better organization
- Cleanup of offset settings
- Hide sticky tabs on narrow viewports
- Improved responsive layout (#3702)
User Experience
- Modal alerts/confirmations on delete/clear operations (#3693, #3598, #3382)
- Auto-add https:// to URLs in quickwatch form if not present
- Better redirect handling on login (#3699)
- 'Recheck all' now returns to correct group/tag (#3673)
- Language set redirect keeps hash fragment
- More friendly human-readable text throughout UI
Performance & Reliability
Scheduler & Processing
- Soft delays instead of blocking time.sleep() calls (#3710)
- More resilient handling of same UUID being processed (#3700)
- Better Puppeteer timeout handling
- Improved Puppeteer shutdown/cleanup (#3692)
- Requests cleanup now properly async
History & Rendering
- Faster server-side "difference" rendering on History page (#3442)
- Show ignored/triggered rows in history
- API: Retry watch data if watch dict changed (more reliable)
API Improvements
- Watch get endpoint: retry mechanism for changed watch data
- WatchHistoryDiff API endpoint includes extra format args (#3703)
Testing Improvements
- Replace time.sleep with wait_for_notification_endpoint_output (#3716)
- Test for mode switching (#3701)
- Test for #3720 added (#3725)
- Extract-text difference test fixes
- Improved dev workflow
Bug Fixes
- Notification error text output (#3672, #3669, #3280)
- HTML validation fixes (#3704)
- Template discovery path fixes
- Notification debug log now uses system locale for dates/times
- Puppeteer spelling mistake in log output
- Recalculation on anchor change
- Queue bubble update disabled temporarily
Dependency Updates
- beautifulsoup4 updated (#3724)
- psutil 7.1.0 → 7.2.1 (#3723)
- python-engineio ~=4.12.3 → ~=4.13.0 (#3707)
- python-socketio ~=5.14.3 → ~=5.16.0 (#3706)
- flask-socketio ~=5.5.1 → ~=5.6.0 (#3691)
- brotli ~=1.1 → ~=1.2 (#3687)
- lxml updated (#3590)
- pytest ~=7.2 → ~=9.0 (#3676)
- jsonschema ~=4.0 → ~=4.25 (#3618)
- pluggy ~=1.5 → ~=1.6 (#3616)
- cryptography 44.0.1 → 46.0.3 (security) (#3589)
Documentation
- README updated with viewport size setup information
Development Infrastructure
- Dev container only built on dev branch
- Improved dev workflow tooling