www/firefox: Update to 152.0.6
* WebGL does not work. webgl.out-of-process workaround was removed.
Disable WebGL by default.
Cnangelog:
152.0.6:
New
* Smart Window includes several enhancements:
Fixed
* Fixed an issue that prevented email tracking protection from being disabled
in the redesigned Firefox Settings. (Bug 2049331)
* Fixed a hang that could occur after using a file picker dialog on macOS 26.
(Bug 2053177)
* Fixed the homepage not loading for some enterprise configurations that set
[189 lines not shown]
py-gitpython: updated to 3.1.52
3.1.52
A security fix for
https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-rwj8-pgh3-r573.
3.1.51
This is primarily a security release. It prevents additional argument-injection
paths that could allow execution of arbitrary commands or writing to arbitrary
files through unsafe Git options (GHSA-956x-8gvw-wg5v), and closes bypasses of
the existing protections using abbreviated long options or joined short options
(GHSA-2f96-g7mh-g2hx).
The release also improves support for relative worktree paths and diffs against
the empty tree, preserves stderr from failed diff processes, supports relative
configuration include paths, and includes assorted documentation, typing, test,
and CI improvements.
py-tibs: updated to 1.0.0
1.0.0
This is the first stable release. The documented public API is now intended
to remain compatible across future 1.x releases.
Backwardly incompatible changes
* Tightened automatic promotion to `Tibs` and `Mutibs`. Constructors and other
bit-sequence arguments now accept only unambiguous inputs: existing
`Tibs`/`Mutibs` objects, strings, `bytes`/`bytearray`/`memoryview`, and strict
list or tuple bit patterns containing only `True`, `False`, `0` or `1`.
Arbitrary iterables, file-like objects such as `io.BytesIO`, `array.array`,
and numeric lists such as `[1, 2, 3]` no longer silently convert through
truthiness. Use `from_bools(...)` for truthy iterables, `from_bytes(...)` for
explicit byte data, and `from_values(...)` for fixed-width numeric values.
py-cloudflare: updated to 5.5.0
5.5.0 (2026-07-10)
Breaking Changes
* **ssl:** The `recommendations` sub-resource has been removed. `client.ssl.recommendations.get()` and the `RecommendationGetResponse` type are no longer available.
* **email_routing:** The `list` method has been removed from `client.email_routing.rules`. Only `create`, `update`, `delete`, and `get` remain. The `RuleListParams` type has been removed.
* **zero_trust:** The `UserPolicyCheckGeo` type has been removed from `cloudflare.types.zero_trust.access.applications`. The geo information is now inlined as `UserIdentityGeo` within `UserPolicyCheckListResponse`.
* **zero_trust:** The pagination type for `client.zero_trust.devices.ip_profiles.list()` changed from `SyncSinglePage` to `SyncV4PagePaginationArray`. Code that relied on single-page iteration semantics may need adjustment.
* **aisearch:** The `SourceParamsWebCrawlerStoreOptions` type and the `store_options` field on `SourceParamsWebCrawler` have been removed from instance create/update params and responses. The `parse_type` enum value `"feed-rss"` has been removed (only `"sitemap"` and `"crawl"` remain). The `search_query` field on `InstanceSearchResponse` and `NamespaceSearchResponse` changed from required `str` to `Optional[str]`. A new required `query_kind` field (`Literal["text", "image", "multimodal"]`) has been added to search responses.
* **zero_trust:** In `Organization` and related params, `MfaSSHPivKeyRequirements` has been renamed to `MfaPivKeyRequirements`, the `mfa_ssh_piv_key_requirements` field has been renamed to `mfa_piv_key_requirements`, and the `allowed_authenticators` enum value `"ssh_piv_key"` has been changed to `"piv_key"`.
Features
* **email_auth:** add email_auth resource
* **moq:** add moq resource
* **logs:** add log_explorer sub-resource with query, datasets, and available datasets
* **email_security:** add bulk message operations to investigate
[10 lines not shown]
py-python-discovery: updated to 1.4.4
Bug fixes - 1.4.4
- Parse the debug build flag in interpreter specs - ``python3.13d`` and Debian's ``python3.13-dbg`` /
``python3.13-debug`` now select a ``Py_DEBUG`` interpreter instead of being misread as an ISA named ``dbg``.
Resolving a virtualenv to its base interpreter also checks the free-threaded and debug ABI flags, so a debug or
free-threaded environment no longer resolves to a release build of the same version
py-peewee: updated to 4.2.3
4.2.3
* Fix a compound select (`UNION`/`INTERSECT`/`EXCEPT`) used as a correlated
subquery emitting a phantom alias for the correlated outer table in every
branch but the left-most, producing invalid SQL (e.g. `no such column:
t4.id`). The right-hand branch renders in a fresh alias scope that no longer
resolved the outer source's existing alias, it now inherits the enclosing
scope's aliases while still assigning fresh aliases to its own sources.
* Fix full-text search `weights` passed as a `dict` being mis-applied to the
wrong columns. For FTS3/4 the implicit `docid` primary-key was included when
building the weight list, shifting every column by one (raising `IndexError`
with the Python ranking UDF, silently mis-scoring with the Cython one), for
FTS5, `UNINDEXED` columns were skipped even though `bm25()` weights are
positional across all columns. The list form of `weights` was unaffected.
* Fix `.cte()` clearing the source query's CTE list in place: converting a query
that carried a `with_cte(...)` clause into a CTE stripped the clause from that
query, so reusing it afterward referenced an undeclared CTE. The query is now
[25 lines not shown]
py-lmdb: updated to 2.3.0
2.3.0
Bug fixes
- ``lmdb.aio``: an async write transaction is now pinned to a private
single-thread executor, so its ``begin``, operations, and
``commit``/``abort`` all run on one OS thread. Previously they were
dispatched across the shared, multi-threaded default executor, which could
release LMDB's thread-bound robust write mutex on the wrong thread (the
failure mode of 465). ``AsyncCursor``/``AsyncEnvironment`` close on
context exit now also acquire the lock and run on the executor, so closing
can no longer race an in-flight operation on the same transaction.
- Fix committing values larger than ~2 GiB. A single LMDB value is written
in one call, exceeding per-call platform write limits: on POSIX,
``write()`` returns a short count that was treated as fatal, so the
commit failed with ``mdb_txn_commit: Input/output error``; the bundled
[63 lines not shown]
