chore(deps): bump the python-minor-patch group with 5 updates

[dependabot]

Bumps the python-minor-patch group with 5 updates:

Package	From	To
flet	0.86.1	0.86.2
ruff	0.15.22	0.16.0
ty	0.0.61	0.0.63
assertpy2	2.17.0	2.18.0
hypothesis	6.157.0	6.161.5

Updates flet from 0.86.1 to 0.86.2

Release notes

Sourced from flet's releases.

v0.86.2

Bug fixes

• Fix code edits not taking effect under flet debug android: after re-running the command, the app kept executing the previously-unpacked, stale code instead of your changes. flet debug rebuilds and reinstalls the same-version APK on each iteration (flutter run does an update install that preserves app data), and serious_python's on-device extraction cache — keyed only on versionName+versionCode — never saw the version change, so it skipped re-unpacking the new app.zip. Bumps serious_python to 4.3.4, which folds the APK's lastUpdateTime into that cache key so every (re)install re-extracts the current code while ordinary relaunches still hit the cache. flet build apk was never affected (#6682) by @​FeodorFitsner.
• Fix an embedded FletApp (an app rendered inside another Flet app — e.g. a preview or gallery host that runs example apps in-process) not refreshing its UI in response to events. Auto-update mode was tracked as components_mode on a single process-global context singleton, so a host app that rendered via page.render/page.render_views turned components mode on process-wide and context.auto_update_enabled() then returned False for the embedded app too — any handler that mutated a control without calling .update() (the common imperative style, including all page.services sensor readings) silently never re-rendered. Event dispatch also ran in a fresh task whose page context var could carry a different session's page, so context-derived state resolved against the wrong session. components_mode is now stored per-Session, and Session.dispatch_event binds the page context to its own session before invoking handlers, so multiple Flet apps sharing one process keep independent update behavior by @​FeodorFitsner.
• Modernize examples for 0.86: replace the removed TextField.error_text with error (chat tutorial, mind_queue, palette_editor), and declare the device permissions each sensor example needs to run on-device — NSMotionUsageDescription on iOS for the motion/barometer sensors and android.permission.VIBRATE for HapticFeedback by @​FeodorFitsner.
• Fix opening a flet run --ios / --android app URL in a desktop browser: the page loaded but stayed on the boot screen, endlessly retrying a WebSocket connection to ws://<host>:<port>/ws. Mobile-mode apps are mounted under a non-root path (e.g. /counter/main.py), so the real WebSocket route lives at /counter/main.py/ws - but since 1.0 Alpha the FastAPI wrapper always passed the bare default ws endpoint name into FletStaticFiles, bypassing its mount-path-aware fallback, and index.html got patched with flet.webSocketEndpoint="ws", which the web client resolves against the server root. The native iOS/Android client derives the path from the page URL and was unaffected. A relative WebSocket endpoint is now resolved against the app mount path when patching index.html, fixing browser access to any Flet web app mounted under a non-root path (--ios/--android, flet run --name, or a flet_web.fastapi app mounted at a sub-path) by @​FeodorFitsner.
• Fix web RawImage and MatplotlibChart animations flooding the console with uncatchable engine exceptions (and breaking the animation) after the browser tab was backgrounded for a while and then refocused. On Flet web the frame producer runs in a Pyodide worker (or on a remote server over a WebSocket) that the browser never throttles, while the client's Flutter frame pipeline is suspended whenever the tab is hidden - so setState schedules frames that never paint and the post-frame callbacks that dispose replaced ui.Images never fire. Decoded images and pending disposals then pile up unbounded in the Dart heap and flush into the engine all at once on resume, one exception per queued frame. This is a client-side accumulation independent of transport, so it also affected native windows minimized with an animation running. Fixed in two layers: (1) a shared FrameStreamVisibility client-side mixin - used by both RawImage and flet-charts' MatplotlibChartCanvas - stops decoding/uploading and frees replaced images immediately while hidden (keeping only cheap offscreen state up to date, so incremental matplotlib diffs stay correct), then presents just the latest frame on resume; (2) a new page.wait_until_visible() gate (driven by on_app_lifecycle_state_change, alongside a page.app_visible property) that the streaming controls await internally, so producer loops park while hidden instead of rendering frames a suspended client can only discard (#6691) by @​FeodorFitsner.
• Fix flet build / flet publish flooding non-interactive logs (CI, cloud build, any piped stdout) with thousands of progress-spinner frames, and fix the --no-rich-output flag not actually producing plain output. The CLI's rich Console was created with force_terminal=True whenever the FLET_CLI_NO_RICH_OUTPUT env var was unset, which forces the Live status spinner to repaint even when stdout isn't a TTY — so in a pipe every animation frame lands on its own line (e.g. hundreds of ( ● ) Initializing web build... lines). And the --no-rich-output CLI flag never reached that console at all: it's parsed per-command, after the module-level console is already built, so it only suppressed emojis while color and the spinner kept going. Now the console auto-detects the terminal (force_terminal=None) — interactive terminals keep the animated spinner while piped output stays quiet — and both FLET_CLI_NO_RICH_OUTPUT and --no-rich-output (detected from sys.argv at import) force fully plain output by @​FeodorFitsner.

Improvements

• Flutter updated to 3.44.7.
• Fix flet_video.Video resetting its volume (and pitch, playback_rate, shuffle_playlist, playlist_mode, subtitle_track) to the player's defaults after toggling visible off then on — e.g. volume jumped back to 100. Hiding a Video disposes its native media_kit player and showing it recreates a fresh one at default settings; the "last-applied" tracking now lives with the player (not the persistent control model) and is reset on recreation, so build() re-applies every setting to the new player (#6683, #6694) by @​ndonkoHenri.
• Fix SearchBar.on_tap_outside_bar not firing when the user tapped outside the open search view. That case now has a dedicated SearchBar.on_tap_outside_view event (fired when tapping outside the open view, e.g. to dismiss it), and on_tap_outside_bar is documented to match what it actually does: fire while the bar is focused and the view is closed, like TextField.on_tap_outside (#6593, #6697) by @​ndonkoHenri.
• Add a --android-legacy-packaging flag (and [tool.flet.android].legacy_packaging setting) to flet build apk/aab for opting into legacy Android native-library packaging. By default (modern packaging), native .so files are stored uncompressed and page-aligned in the APK and memory-mapped directly at runtime, which typically gives a smaller install and Play Store download but a larger raw .apk file. Enabling this option sets useLegacyPackaging = true so the .so are compressed inside the APK and extracted to disk on install: the raw .apk file is smaller (handy when side-loading), at the cost of a larger on-device install and slower native-library loading. The extraction directory is exposed to Python as ANDROID_NATIVE_LIBRARY_DIR, which can help custom native-library consumers that require a real filesystem path. See Native library packaging by @​FeodorFitsner.

Full Changelog: v0.86.1...v0.86.2

Changelog

Sourced from flet's changelog.

0.86.2

Bug fixes

• Fix code edits not taking effect under flet debug android: after re-running the command, the app kept executing the previously-unpacked, stale code instead of your changes. flet debug rebuilds and reinstalls the same-version APK on each iteration (flutter run does an update install that preserves app data), and serious_python's on-device extraction cache — keyed only on versionName+versionCode — never saw the version change, so it skipped re-unpacking the new app.zip. Bumps serious_python to 4.3.4, which folds the APK's lastUpdateTime into that cache key so every (re)install re-extracts the current code while ordinary relaunches still hit the cache. flet build apk was never affected (#6682) by @​FeodorFitsner.
• Fix an embedded FletApp (an app rendered inside another Flet app — e.g. a preview or gallery host that runs example apps in-process) not refreshing its UI in response to events. Auto-update mode was tracked as components_mode on a single process-global context singleton, so a host app that rendered via page.render/page.render_views turned components mode on process-wide and context.auto_update_enabled() then returned False for the embedded app too — any handler that mutated a control without calling .update() (the common imperative style, including all page.services sensor readings) silently never re-rendered. Event dispatch also ran in a fresh task whose page context var could carry a different session's page, so context-derived state resolved against the wrong session. components_mode is now stored per-Session, and Session.dispatch_event binds the page context to its own session before invoking handlers, so multiple Flet apps sharing one process keep independent update behavior by @​FeodorFitsner.
• Modernize examples for 0.86: replace the removed TextField.error_text with error (chat tutorial, mind_queue, palette_editor), and declare the device permissions each sensor example needs to run on-device — NSMotionUsageDescription on iOS for the motion/barometer sensors and android.permission.VIBRATE for HapticFeedback by @​FeodorFitsner.
• Fix opening a flet run --ios / --android app URL in a desktop browser: the page loaded but stayed on the boot screen, endlessly retrying a WebSocket connection to ws://<host>:<port>/ws. Mobile-mode apps are mounted under a non-root path (e.g. /counter/main.py), so the real WebSocket route lives at /counter/main.py/ws - but since 1.0 Alpha the FastAPI wrapper always passed the bare default ws endpoint name into FletStaticFiles, bypassing its mount-path-aware fallback, and index.html got patched with flet.webSocketEndpoint="ws", which the web client resolves against the server root. The native iOS/Android client derives the path from the page URL and was unaffected. A relative WebSocket endpoint is now resolved against the app mount path when patching index.html, fixing browser access to any Flet web app mounted under a non-root path (--ios/--android, flet run --name, or a flet_web.fastapi app mounted at a sub-path) by @​FeodorFitsner.
• Fix web RawImage and MatplotlibChart animations flooding the console with uncatchable engine exceptions (and breaking the animation) after the browser tab was backgrounded for a while and then refocused. On Flet web the frame producer runs in a Pyodide worker (or on a remote server over a WebSocket) that the browser never throttles, while the client's Flutter frame pipeline is suspended whenever the tab is hidden - so setState schedules frames that never paint and the post-frame callbacks that dispose replaced ui.Images never fire. Decoded images and pending disposals then pile up unbounded in the Dart heap and flush into the engine all at once on resume, one exception per queued frame. This is a client-side accumulation independent of transport, so it also affected native windows minimized with an animation running. Fixed in two layers: (1) a shared FrameStreamVisibility client-side mixin - used by both RawImage and flet-charts' MatplotlibChartCanvas - stops decoding/uploading and frees replaced images immediately while hidden (keeping only cheap offscreen state up to date, so incremental matplotlib diffs stay correct), then presents just the latest frame on resume; (2) a new page.wait_until_visible() gate (driven by on_app_lifecycle_state_change, alongside a page.app_visible property) that the streaming controls await internally, so producer loops park while hidden instead of rendering frames a suspended client can only discard (#6691) by @​FeodorFitsner.
• Fix flet build / flet publish flooding non-interactive logs (CI, cloud build, any piped stdout) with thousands of progress-spinner frames, and fix the --no-rich-output flag not actually producing plain output. The CLI's rich Console was created with force_terminal=True whenever the FLET_CLI_NO_RICH_OUTPUT env var was unset, which forces the Live status spinner to repaint even when stdout isn't a TTY — so in a pipe every animation frame lands on its own line (e.g. hundreds of ( ● ) Initializing web build... lines). And the --no-rich-output CLI flag never reached that console at all: it's parsed per-command, after the module-level console is already built, so it only suppressed emojis while color and the spinner kept going. Now the console auto-detects the terminal (force_terminal=None) — interactive terminals keep the animated spinner while piped output stays quiet — and both FLET_CLI_NO_RICH_OUTPUT and --no-rich-output (detected from sys.argv at import) force fully plain output by @​FeodorFitsner.

Improvements

• Flutter updated to 3.44.7.
• Fix flet_video.Video resetting its volume (and pitch, playback_rate, shuffle_playlist, playlist_mode, subtitle_track) to the player's defaults after toggling visible off then on — e.g. volume jumped back to 100. Hiding a Video disposes its native media_kit player and showing it recreates a fresh one at default settings; the "last-applied" tracking now lives with the player (not the persistent control model) and is reset on recreation, so build() re-applies every setting to the new player (#6683, #6694) by @​ndonkoHenri.
• Fix SearchBar.on_tap_outside_bar not firing when the user tapped outside the open search view. That case now has a dedicated SearchBar.on_tap_outside_view event (fired when tapping outside the open view, e.g. to dismiss it), and on_tap_outside_bar is documented to match what it actually does: fire while the bar is focused and the view is closed, like TextField.on_tap_outside (#6593, #6697) by @​ndonkoHenri.
• Add a --android-legacy-packaging flag (and [tool.flet.android].legacy_packaging setting) to flet build apk/aab for opting into legacy Android native-library packaging. By default (modern packaging), native .so files are stored uncompressed and page-aligned in the APK and memory-mapped directly at runtime, which typically gives a smaller install and Play Store download but a larger raw .apk file. Enabling this option sets useLegacyPackaging = true so the .so are compressed inside the APK and extracted to disk on install: the raw .apk file is smaller (handy when side-loading), at the cost of a larger on-device install and slower native-library loading. The extraction directory is exposed to Python as ANDROID_NATIVE_LIBRARY_DIR, which can help custom native-library consumers that require a real filesystem path. See Native library packaging by @​FeodorFitsner.

Commits

• 2b0c23a Fix hidden-tab frame flood in RawImage and MatplotlibChart web animations (#6...
• a0e4697 feat(android): add --android-legacy-packaging flag and legacy_packaging setti...
• a700498 fix(SearchBar): fire on_tap_outside_view when tapping outside the open vi...
• d18f14b Fix embedded FletApp auto-update and WebSocket connection for non-root-mounte...
• 5af0f4e Prepare 0.86.2 release: fix stale code under flet debug android (serious_py...
• 158978d Blog post: Smarter Flet Studio with AI Agent (#6689)
• See full diff in compare view

Updates ruff from 0.15.22 to 0.16.0

Release notes

Sourced from ruff's releases.

0.16.0

Release Notes

Released on 2026-07-23.

Check out the blog post for a migration guide and overview of the changes!

Breaking changes

• Ruff now enables a much larger set of rules by default (413, up from 59). See the blog post for more details and the new Default Rules page for a full listing of the enabled rules. Note that this is primarily an expansion, but 18 of the more opinionated pycodestyle (E) and pyflakes (F) rules have been removed from the default set: E401, E402, E701, E702, E703, E711, E712, E713, E714, E721, E731, E741, E742, E743, F403, F405, F406, and F722.

• Ruff can now format Python code blocks in Markdown files and will do this by default. See the documentation for more details.

• Ruff now supports ruff: ignore comments at the ends of lines, like noqa comments, or on the line preceding a diagnostic. For example, these both suppress an unused-import (F401) diagnostic:

  import math  # ruff: ignore[F401]
  ruff: ignore[F401]
  import os

• Fixes are now shown in check and format --check output:

  ❯ ruff format --check .
  unformatted: File would be reformatted
   --> try.md:1:1
    |
  1 | ```python
    - import   math
  2 + import math
  3 | ```
    |
  1 file would be reformatted

  This example also shows off the Markdown formatting.

• format --check now supports the same output formats as the linter, including the github and gitlab outputs for rendering annotations in CI:

  ❯ ruff format --check --output-format github .
  ::error title=ruff (unformatted),file=try.md,line=2,col=8,endLine=2,endColumn=10::try.md:2:8: unformatted: File would be reformatted

  See the CLI help or documentation for the full list of supported formats.

• The filename, location, end_location, fix.edits[].location, and fix.edits[].end_location fields in the JSON output format may now be null rather than defaulting to the empty string and row 1, column 1, respectively.

... (truncated)

Changelog

Sourced from ruff's changelog.

0.16.0

Released on 2026-07-23.

Check out the blog post for a migration guide and overview of the changes!

Breaking changes

• Ruff now enables a much larger set of rules by default (413, up from 59). See the blog post for more details and the new Default Rules page for a full listing of the enabled rules. Note that this is primarily an expansion, but 18 of the more opinionated pycodestyle (E) and pyflakes (F) rules have been removed from the default set: E401, E402, E701, E702, E703, E711, E712, E713, E714, E721, E731, E741, E742, E743, F403, F405, F406, and F722.

• Ruff can now format Python code blocks in Markdown files and will do this by default. See the documentation for more details.

• Ruff now supports ruff: ignore comments at the ends of lines, like noqa comments, or on the line preceding a diagnostic. For example, these both suppress an unused-import (F401) diagnostic:

  import math  # ruff: ignore[F401]
  ruff: ignore[F401]
  import os

• Fixes are now shown in check and format --check output:

  ❯ ruff format --check .
  unformatted: File would be reformatted
   --> try.md:1:1
    |
  1 | ```python
    - import   math
  2 + import math
  3 | ```
    |
  1 file would be reformatted

  This example also shows off the Markdown formatting.

• format --check now supports the same output formats as the linter, including the github and gitlab outputs for rendering annotations in CI:

... (truncated)

Commits

• a2635fd Bump 0.16.0 (#27136)
• 3433449 [ty] Reuse full call diagnostics for implicit setter calls (#27115)
• 2240070 Reflect ruff: ignore and --add-ignore stabilization in documentation (#27...
• 17ef711 Stabilize --add-ignore (#27125)
• ef912bb Add newly stabilized rules to defaults (#27055)
• b30f040 Stabilize new default rules (#27035)
• bcd70c5 Exclude Markdown files from format-dev runs (#27052)
• 87e51e2 Fix format --check spans for syntax errors (#27045)
• afe2723 [flake8-gettext] Stabilize qualified-name and built-in binding resolution (...
• a9702d8 [flake8-bandit] Stabilize string literal binding resolution (S310) (#26944)
• Additional commits viewable in compare view

Updates ty from 0.0.61 to 0.0.63

Release notes

Sourced from ty's releases.

0.0.63

Release Notes

Released on 2026-07-23.

Core type checking

• Handle generic stringified PEP 613 (typing.TypeAlias) type aliases (#27092)
• Allow equality narrowing across non-final classes (#27031)
• Allow interpolated string literals to be promoted to str (#27104)
• Fix double specialization of generic type aliases (#27058)
• Fix intersections of type and TypeForm (#27099)
• When narrowing from a match statement leads a variable x to be inferred as A & B, infer the type of x.attr as <type of A.attr> & <type of B.attr> (#27103)

Library support

• Pydantic: Stricter validation of sub-model fields in lax mode (#27091)
• Pydantic: Support special underscore parameters in BaseSettings models (#27098)

Performance

• Avoid exponential narrowing of optional dynamic match subjects (#27100)
• Avoid normalizing cached absolute file paths (#26998)

Contributors

• @​sharkdp
• @​charliermarsh
• @​ibraheemdev
• @​carljm

Install ty 0.0.63

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://releases.astral.sh/github/ty/releases/download/0.0.63/ty-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://releases.astral.sh/github/ty/releases/download/0.0.63/ty-installer.ps1 | iex"

Download ty 0.0.63

File	Platform	Checksum
ty-aarch64-apple-darwin.tar.gz	Apple Silicon macOS	checksum

... (truncated)

Changelog

Sourced from ty's changelog.

0.0.63

Released on 2026-07-23.

Core type checking

• Handle generic stringified PEP 613 (typing.TypeAlias) type aliases (#27092)
• Allow equality narrowing across non-final classes (#27031)
• Allow interpolated string literals to be promoted to str (#27104)
• Fix double specialization of generic type aliases (#27058)
• Fix intersections of type and TypeForm (#27099)
• When narrowing from a match statement leads a variable x to be inferred as A & B, infer the type of x.attr as <type of A.attr> & <type of B.attr> (#27103)

Library support

• Pydantic: Stricter validation of sub-model fields in lax mode (#27091)
• Pydantic: Support special underscore parameters in BaseSettings models (#27098)

Performance

• Avoid exponential narrowing of optional dynamic match subjects (#27100)
• Avoid normalizing cached absolute file paths (#26998)

Contributors

• @​sharkdp
• @​charliermarsh
• @​ibraheemdev
• @​carljm

0.0.62

Released on 2026-07-21.

Bug fixes

• Guard recursive Protocol and TypedDict relations (#26990)
• Prevent stack overflows in recursive type relation checks (#26503)
• Recover from cancelled file indexing (#26876)

Diagnostics

• Avoid editing ignore comments with trailing reasons (#26939)
• Prefer innermost inline suppressions (#26940)
• Remove unused own-line ignore comments (#27013)
• Reuse applicable own-line suppressions in --add-ignore (#26925)

Configuration

• Respect rules and analysis in PEP 723 script metadata configurations (#26671)

... (truncated)

Commits

• 46f4915 Bump version to 0.0.63 (#4071)
• df75992 Bump version to 0.0.62 (#4057)
• 48dd1fd Update prek dependencies (#4059)
• f53a95e Update astral-sh/setup-uv action to v9 (#4060)
• 17d1791 Update dependency prek to v0.4.9 (#4058)
• eb7e7ba Update documentation on mypy/pyright --strict parity, and achieving maximum...
• See full diff in compare view

Updates assertpy2 from 2.17.0 to 2.18.0

Release notes

Sourced from assertpy2's releases.

2.18.0

TL;DR

Change	What it gives you
Vacuity guard	an opt-in warning when a universal assertion passes over an empty value
Naive and aware datetimes	fix: the ignoring-precision assertions refuse the mixed pair instead of passing
extracting(sort=...)	fix: an invalid sort arg is rejected rather than silently ignored
is_subset_of()	fix: dicts and lists as items work, the way the containment family already allowed
Matcher combinators	fix: & and | reject a non-matcher where the combinator is written
Circular references	fix: the snapshot and shape walkers report the cycle instead of a RecursionError
Near-timeout polls	a run-end report naming the polls that converged against their deadline, with a bar you can move
Snapshot mismatches	the failure names the snapshot file and the flag that accepts the new value
Inline snapshots	a mismatch says how to rewrite the literal in place
assert_conforms()	pydantic validation errors become structured diff rows, one per field
Soft and warn failures	the diff reaches soft_assertions() and assert_warn(), not only hard failures
Pipeline provenance	an empty-value failure says which step emptied it
Ordering and duplicates	the longest run that matched, and which values were repeated
any_satisfy()	the items that were examined, instead of only "none did"

Assertions that checked nothing

A universal assertion over an empty collection is true by definition. all_satisfy() on an empty list passes without calling the predicate once, and so does every sibling that quantifies over items.

That is correct logic and a common way for a test to stop testing anything. The fixture stops producing rows, the filter stops matching, and the assertion keeps passing.

The guard is opt-in, because an empty subject is legitimate as often as it is a bug. Turn it on with --assertpy2-vacuous or ASSERTPY2_VACUOUS=1, and silence individual call sites with allow_empty=True.

def test_archived_orders_are_settled():
    archived_orders = []
    assert_that(archived_orders).all_satisfy(lambda order: order.total > 0)

Before

1 passed in 0.11s

Now, with the flag:

1 passed, 1 warning in 0.10s
VacuousAssertionWarning: all_satisfy() passed over an empty value, so nothing was

checked. Pass allow_empty=True if that is intended.

... (truncated)

Commits

• 0df7a8b chore: release 2.18.0
• 1458172 build: bump ty to 0.0.63
• cf0a64e build: bump ty to 0.0.62
• 618f31e feat: let the near-timeout poll report be tuned or turned off
• fc56fc2 perf: read the vacuity environment switch once instead of per assertion
• 892990d docs: cover the new guards and reports, and clear the prose walls
• 5f0d274 feat: show the examined items when any_satisfy finds no match
• f533e60 feat: name what broke in ordering and duplicate containment failures
• abfe6e7 fix: reject a non-matcher operand where the combinator is written
• c16a478 fix: detect circular references in the shape and snapshot walkers
• Additional commits viewable in compare view

Updates hypothesis from 6.157.0 to 6.161.5

Commits

• 6c5ec2a Bump hypothesis version to 6.161.5 and update changelog
• d92f4d2 Merge pull request #4821 from Zac-HD/claude/snapshots-ci-and-test-fixes-xzo6qq
• 608d980 Build the website in PR CI, and upload it as an artifact
• 39a65a0 Run the snapshot tests in CI
• abc4301 Skip the inaccessible-database test when running as root
• 4a1f7a1 Key lambda descriptions on the wrapped function, not the wrapper
• 3ba4130 Bump hypothesis version to 6.161.4 and update changelog
• b794004 Merge pull request #4819 from Liam-DeVoe/riscv64-wheels
• 6a6f811 Bump hypothesis version to 6.161.3 and update changelog
• 882e5ea Merge pull request #4817 from Zac-HD/claude/hypothesis-issue-4149-proxies-16nmgw
• Additional commits viewable in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions