lotobo/av-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

chore: prepare av-tools 0.3.0 release

Browse Source
This commit is contained in:
Albrecht Degering
2026-07-27 18:38:20 +02:00
parent f2c0fc12d2
commit 597ea044b6
13 changed files with 49 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/FORMAT_SUPPORT.md
View File

@@ -5,7 +5,7 @@ extensions or this document. The app queries muxers, demuxers, decoders,
encoders and filters; a preset is disabled with missing components listed.
Browser playback is a separate capability checked with MIME/media APIs.
## 0.2.1 release fixture matrix
## 0.3.0 release fixture matrix
All 15 files are generated and re-probed with native FFmpeg 7.1.3 for test
preparation and pass the checksum/probe verifier. That proves fixture

4
docs/KNOWN_LIMITATIONS.md
View File

@@ -1,6 +1,6 @@
# Known limitations
This is the conservative 0.2.1 release baseline. A capability appearing in
This is the conservative 0.3.0 release baseline. A capability appearing in
FFmpeg output does not remove these product/browser/resource limits.
## Functional
@@ -82,7 +82,7 @@ FFmpeg output does not remove these product/browser/resource limits.
verification against the live container.
- The application is GPL-3.0-or-later and its native legal files and pinned
source identities are included in the release record. Publish the production
ZIP/checksum, exact `v0.2.1` source and FFmpeg Corresponding Source bundle
ZIP/checksum, exact `v0.3.0` source and FFmpeg Corresponding Source bundle
together; development-only smoke artifacts must not be distributed.
- Chromium covers a broad real pinned-core ST operation matrix, a real MT
H.264/AAC conversion, MT-to-ST fallback, nested static/Toolbox-context

12
docs/RELEASE.md
View File

@@ -11,7 +11,7 @@ The repository already declares the application licence and immutable
third-party source identities. Before any distribution:
1. commit the reviewed GPL-3.0-or-later source;
2. create and verify annotated tag `v0.2.1` at that exact commit;
2. create and verify annotated tag `v0.3.0` at that exact commit;
3. push the commit and tag to the canonical public repository;
4. assemble, review and publish corresponding source and exact external
notices for both reviewed core profiles and linked libraries;
@@ -57,8 +57,8 @@ npm run package:release -- --allow-unlicensed-development-smoke
Pass `--force` only to replace the exact same-version ZIP and sidecar. Output:
```text
release/av-tools-0.2.1.zip
release/av-tools-0.2.1.zip.sha256
release/av-tools-0.3.0.zip
release/av-tools-0.3.0.zip.sha256
release/ffmpeg-core-0.12.10-reviewed-stack5m.1-corresponding-source.tar.xz
release/ffmpeg-core-0.12.10-reviewed-stack5m.1-corresponding-source.tar.xz.sha256
```
@@ -68,7 +68,7 @@ Verify independently:
```sh
node scripts/checksum-release.mjs
(cd release && sha256sum -c ffmpeg-core-0.12.10-reviewed-stack5m.1-corresponding-source.tar.xz.sha256)
unzip -l release/av-tools-0.2.1.zip
unzip -l release/av-tools-0.3.0.zip
tar -tJf release/ffmpeg-core-0.12.10-reviewed-stack5m.1-corresponding-source.tar.xz
```
@@ -96,7 +96,7 @@ exact `HEAD` and clones that revision into a temporary directory:
```sh
npm run portal:smoke -- \
--artifact release/av-tools-0.2.1.zip \
--artifact release/av-tools-0.3.0.zip \
--portal-root ../toolbox-portal
```
@@ -123,7 +123,7 @@ for `v0.6.0` and must not suppress review of new gaps. See
## 5. Publish only reviewed bytes
From a clean `v0.2.1` checkout, rerun all checks, create the ZIP once, verify
From a clean `v0.3.0` checkout, rerun all checks, create the ZIP once, verify
the sidecar, assemble that exact ZIP through Portal, and publish the immutable
ZIP, `.zip.sha256`, manifest, changelog, Corresponding Source and notices. Put
its exact lowercase digest/version/id/target in a reviewed Portal lock. Never