* Decode AVIF through shared image codecs
* Include JPEG encoder distribution notices
* Exercise AVIF HDR decoding through public API
* Preserve AVIF source bit depth
* Test AVIF alpha through public entrypoints
* Update AVIF round trip for supported decode
* Document native AVIF decode support
* Clarify import feature gates
* Keep RAW fixtures valid under shared container and strip bounds
* Include sample-to-chunk mappings in CR3 fixtures
* Find Similar test: a photo read from memory isn't a missing read (#3823)
The second search after a stop plans its reads after frames in which the
loupe and filmstrip decoded photos; those are measured from memory
(source_ref takes the cached source), so the drive sees fewer than 12 reads
on a loaded machine. Check instead that no file is read twice, the searched
photo above all; the answer still needs every photo's signature.
* Find Similar test: every photo is measured after the resumed search
* Bound AVIF padded picture storage and preserve integer source flag
* Size the AVIF picture-store budget for the stored canvas, not the clap-cropped size
* Attribute the AVIF lossless decode fixture
* Keep the AVIF clap test helpers free of unwrap for the codecs lint gate
* lightcraft: keep the newer craft-cms pin after merging main
---------
Co-authored-by: Bruno-Alumn <171815746+Bruno-Alumn@users.noreply.github.com>
Co-authored-by: FredApps <153173854+FredApps@users.noreply.github.com>
* Honor CARGO_BUILD_TARGET in FreeBSD packaging for aarch64 release builds
package.sh always built for the host and took the arch from uname -m, so a
cross build (aarch64 in an x86_64 FreeBSD VM) would read the wrong target
directory and name the archive after the VM. With CARGO_BUILD_TARGET set,
pass it to cargo, read target/<triple>/release, and take the arch from the
target. Unset keeps the old behavior.
* Reject unknown CARGO_BUILD_TARGET in FreeBSD packaging
Only the two FreeBSD triples are packaged. Any other target now fails before the
build instead of being labelled x86_64.
* Skip the --version smoke run for cross-built FreeBSD packages
A binary built for another target cannot run on the build host, so under set -e
the run would fail the release after the archive is written.
The policy check now reads the compiled AppSearch and RegLocator rows for the
remembered-folder properties (registry root, key, value name and type for both
scopes) and runs the DIR, FOLDER, PATH and legacy exe actions in sequence order
against seeded values, so their precedence and the preset-folder guard cannot
regress. It also replays the wizard folder actions in sequence order (a
remembered folder beats the new-install default, a typed folder beats both) and
requires the machine restore action between the scope page and costing.
The pre-signing check matched any folder named Program Files, so it rejected
a valid MSI when Windows resolves Program Files elsewhere, accepted the 64-bit
root for an x86 package and accepted a different app name. Build the expected
folder from the package architecture's resolved root and the policy name.
Real msiexec runs (per-user and all-users, silent and wizard) found two defects
that the metadata fixtures cannot see:
- "Only for me" published ALLUSERS=2, so FindRelatedProducts treated the run as
per-machine and skipped the existing per-user copy. An interactive upgrade
left two registered products and uninstall left files behind. The page now
leaves ALLUSERS unset for a per-user choice.
- Windows Installer resolves Program Files once, for the context it started in,
so choosing "Everyone" in the wizard installed into the user profile with a
machine-wide registration. The wizard now sets the new-install folder itself
after the choice (Program Files, Program Files (x86) for 32-bit, or the
per-user Programs folder). Silent installs are unchanged.
check-install-policy.ps1 now fails if either regresses.
Preserve current main, adapt frame/input and IME handling, and keep library
check results stable across layout passes. Include the matching Nix font lock
and reviewed attribution changes.