py-django-compressor: updated to 4.7.0
v4.7 (2025-11-12)
- Drop Python 3.10 (EOL), Add Python 3.15
- Add support for Django 6.1.
- Drop support for Django versions before 5.2.
- Replace deprecated codecs.open with builtin open
- Discover compress blocks inside Jinja2 elif branches
- Update BrotliCompressorFileStorage to compress each file in one go
- Add Subresource Integrity (SRI) support for compressed assets
py-publicsuffixlist: updated to 1.1.2.20261112
1.1.1, 1.1.2 (2026-10-21)
No code changes. This release only refreshes CI and development tooling.
Update astral-sh/setup-uv to v10.3.0 in the GitHub Actions workflows.
Refresh uv.lock, updating certifi to pick up the bundled CA certificate changes.
Fix the auto-release workflow so that it no longer bundles a stale PSL file.
1.1.0 (2026-10-10)
This version drops support for Python 3.5, 3.6 and 3.7, and now requires Python 3.8 or later.
Packaging has been migrated to PEP 621 metadata in pyproject.toml using hatchling, replacing setup.py, setup.cfg and MANIFEST.in. The version is now read from publicsuffixlist.__version__, and development dependencies are locked with uv.
Add PEP 561 py.typed marker and complete type annotations for the public API, including compat and the update script.
Add an accept_unknown keyword argument to is_private() and is_public().
[4 lines not shown]
ports-mgmt/pkg: update to 2.9.1
Changes:
Major changes:
- upgrade: be more verbose about why a package is being installed as part of an upgrade
- improvements in shlibs/provides handling in pkg add (for subpackages in ports).
Minor changes:
- Fix plugins
- Fix elf reading leading to crash
- Fix query %R
- Sync libfetch from current
(cherry picked from commit 603478f9f4b430b8262627d61c8efa3e7cc3fc5a)
ports-mgmt/pkg: update to 2.9.0
Major changes
=============
- Security hardening everywhere
- libpkg: add the pkg_repo_meta_extra() API
- full support for musl
- keys: fall back on the host keys when using a root directory
- pkg set -v: store the vital flag as a user override combined with the
package's own flag
- clean: keep the exact archives of the installed packages
- db: add out-of-schema pkg_local and pkg_attr to improve changes
without schema incompatibilities
- upgrade/install: report why each installed package that the plan
removes
- upgrade/install: require an explicit confirmation before removing
explicitly installed packages
- upgrade/install: require an explicit confirmation before removing
explicitly installed packages
[38 lines not shown]
ports-mgmt/pkg: update to 2.9.1
Changes:
Major changes:
- upgrade: be more verbose about why a package is being installed as part of an upgrade
- improvements in shlibs/provides handling in pkg add (for subpackages in ports).
Minor changes:
- Fix plugins
- Fix elf reading leading to crash
- Fix query %R
- Sync libfetch from current
[InstCombine] Fold binop of selects with implied conditions when only one arm simplifies (#224477)
Transform:
`(P == C0 ? X : Def) + (P == C1 ? Y : 0)`
into:
`P == C0 ? X : (Def + (P == C1 ? Y : 0))`
More generally, when both operands of a binop are one-use selects and
the condition of one implies the condition of the other, so that one arm
simplifies once the other select is resolved, distribute the binop over
the select and create the remaining arm.
This allows for more parts of the expression to be predicated, and
allows more CSE and reuse of nodes calculated as part of an exclusive
sum algorithm.
[2 lines not shown]
[ORC] Make sps::HandlerSpec a base class for handler specs (#241702)
sps::HandlerSpec<Descriptor> becomes sps::HandlerSpec<SPSSig>, a base
class that supplies the SPS signature and the wrap function. Each
handler's spec now derives from it and adds its default tag name:
struct MyHandlerSpec : sps::HandlerSpec<int32_t(int32_t)> {
static constexpr SymbolNameSpec Name =
SymbolNameSpec::c("my_handler_tag");
};
and is bound with bindCallControllerHandler<MyHandlerSpec>(...).
Proxy-side controller-interface descriptors must stay separate from
their ProxySpecs, because the executor side (e.g. OrcTargetProcess) uses
them and cannot depend on ORC's core. Nothing on the executor side uses
handler descriptors, so keeping them separate from their specs only
added an alias per handler.
The in-tree handler descriptors and tests are updated to the new form.
[SPIRV] Skip loop strength reduction for logical SPIR-V (#240603)
LSR can introduce `Private` pointer induction variables that logical
SPIR-V cannot represent, causing `SPIRVLegalizePointerCast` to abort.
Found this while testing the `p:32:32` logical SPIR-V change in
[#239347](https://github.com/llvm/llvm-project/pull/239347), which needs
this fix first.
This skips LSR for logical `spirv` in both pass managers, using a new
`EnableLoopStrengthReduce` flag in `TargetPassConfig` and the existing
`DisableLSR` option. Physical `spirv32` and `spirv64` retain LSR.
Tests:
- `loop-strength-reduce-logical.ll` checks 32-bit and 64-bit integer
array indices under both pass managers, with conditional `spirv-val`
runs.
- `optimizations/add-check-overflow.ll` checks that physical targets
[5 lines not shown]
[mlir] Use the LLVM context library options in ModuleToObject
LLVM targets are moving their flags from `cl::opt` to library options, as
NVPTX did in https://github.com/llvm/llvm-project/pull/238141. A target
machine reads these from the `TargetOptions` it is created with and falls
back to the global values otherwise. `ModuleToObject` created its target
machine with default `TargetOptions`, so the options a client set on the
LLVM context of a serialization never reached code generation, and the
client had to change the global options instead.
Create the target machine with the library options of the LLVM context
when any are set, and keep using the global ones otherwise so that tools
that only parse their command line behave as before. Setting the data
layout and triple no longer creates the target machine, so the initial
LLVM IR callback can still set the options. The target machine now refers
to options owned by the context and is therefore destroyed at the end of
`run`.
Assisted-by: Antigravity
[AMDGPU] Guard tensor load/store intrinsics with tdm-insts feature (#241724)
On subtargets without TDM instructions, such as gfx942, gfx1200 and
gfx1310, these intrinsics crashed instruction selection
[SLP] Pass a lane as the vector cost context only if all lanes agree
getEntryCost prices a vector instruction with one scalar lane as the
context, while each scalar lane is priced in its own context. A target
that reads the context, like the users of an fmul that fuses into an fma
on AMDGPU or a bit select on AArch64, gives the whole vector the property
of that one lane.
Pass the lane as the context only if the vector cost is the same with any
of the represented lanes as the context.
Assisted-by: Claude Opus
[mlir] Use the LLVM context library options in ModuleToObject
LLVM targets are moving their flags from `cl::opt` to library options, as
NVPTX did in https://github.com/llvm/llvm-project/pull/238141. A target
machine reads these from the `TargetOptions` it is created with and falls
back to the global values otherwise. `ModuleToObject` created its target
machine with default `TargetOptions`, so the options a client set on the
LLVM context of a serialization never reached code generation, and the
client had to change the global options instead.
Create the target machine with the library options of the LLVM context
when any are set, and keep using the global ones otherwise so that tools
that only parse their command line behave as before. Setting the data
layout and triple no longer creates the target machine, so the initial
LLVM IR callback can still set the options. The target machine now refers
to options owned by the context and is therefore destroyed at the end of
`run`.
Assisted-by: Antigravity
SysV SHM: make kern_shmat static
This is the opposite of most kern_ cases, but SysV IP is designed to be
loaded as a module and freebsd32 support lives inside the main
implementation file. Arguably it should be in a seperate module with a
dependency, but that's a refactor for another day.
Effort: CHERI upstreaming
Sponsored by: Innovate UK
Pull Request: https://github.com/freebsd/freebsd-src/pull/2284
[mlir] Use the LLVM context library options in ModuleToObject
LLVM targets are moving their flags from `cl::opt` to TableGen-declared
library options read through an `llvm::cl::LibraryOptionsContext`, as
NVPTX did in #238141. IR-level code reads them from the `LLVMContext`,
while a `TargetMachine` reads them from
`TargetOptions::MCOptions.LibraryOptions` and falls back to the global
values when that pointer is null. `ModuleToObject` always created its
target machine with default `TargetOptions`, so options set on the
per-serialization `LLVMContext` never reached code generation. Clients
that need per-module options, such as a GPU serialization pass with its
own LLVM flags, had to mutate the process-wide options instead.
Create the target machine with the library options of the LLVM context
whenever any option is set on it, and keep reading the global options
otherwise, so tools that only parse their command line behave as before.
Setting the data layout and triple now only looks up the target instead
of creating the target machine, which defers its creation until after
`initialLlvmIRCallback` and lets that callback, in addition to
[5 lines not shown]
[OpenMP][libomp] Ensure memory barrier before publishing dn.task = NULL (#240070)
Fixes #237247
On weakly ordered architectures like AArch64, the lock acquire in
KMP_ACQUIRE_DEPNODE does not prevent prior memory writes from the task
body from floating past it. When dn.task = NULL is written, another
thread reading dn.task without locks in __kmp_depnode_link_successor()
can observe NULL before all stores from the predecessor task have
committed, causing dependent tasks to read stale memory.
Insert KMP_MB() before KMP_ACQUIRE_DEPNODE in __kmp_release_deps() to
ensure task body memory writes are visible before the task is marked
finished.
Fixes #237247
Tool disclosure: The patch and unit tests were authored manually; Google
Antigravity was used to review the diff, run local tests, and write this
PR description.
