chore: initial sanitized public snapshot
This commit is contained in:
@@ -0,0 +1,53 @@
|
||||
# aria2-rust-pro 1.0.0
|
||||
|
||||
`aria2-rust-pro 1.0.0` is the first public release published from the
|
||||
self-hosted Gitea repository and its built-in Actions pipeline.
|
||||
|
||||
This release establishes the first automated release lane for the project:
|
||||
|
||||
- Windows host packaging through the Cargo-native `xtask` release flow
|
||||
- portable Docker image tar export through the Cargo-native Docker flow
|
||||
- release manifests and SHA-256 checksum files attached beside the primary
|
||||
artifacts
|
||||
|
||||
## Highlights
|
||||
|
||||
- Rust 2024 rewrite of the current Aria2-Pro-Core line
|
||||
- Cargo-native release packaging and Docker export automation
|
||||
- self-hosted Gitea Actions runner and release workflow for future releases
|
||||
|
||||
## Compatibility Notes
|
||||
|
||||
- version smoke preserves the upstream-compatible first line
|
||||
`aria2 version 1.37.0`
|
||||
- Docker images keep the `aria2c` entrypoint shape by symlinking
|
||||
`aria2c -> aria2-rust-pro`
|
||||
- migration and deployment guides remain in-repo under `docs/migration/` and
|
||||
`docs/deployment/`
|
||||
|
||||
## Artifacts
|
||||
|
||||
This automated release is expected to publish:
|
||||
|
||||
- one Windows MSVC release archive under `dist/release/v1.0.0/`
|
||||
- one Docker image tar under `dist/docker/v1.0.0/`
|
||||
- JSON manifest files for both artifact families
|
||||
- per-file SHA-256 checksums and `SHA256SUMS.txt`
|
||||
|
||||
## Verification
|
||||
|
||||
The release workflow performs:
|
||||
|
||||
- workspace fast gates
|
||||
- nightly `cargo udeps`
|
||||
- `cargo deny`
|
||||
- release version smoke
|
||||
- daemon-free Docker smoke
|
||||
- daemon-backed Docker smoke
|
||||
- local release packaging
|
||||
- Docker image export
|
||||
|
||||
## Known Limits
|
||||
|
||||
- the first release asset set is Windows-first plus Docker image tar
|
||||
- broader multi-platform release archives remain future work
|
||||
Reference in New Issue
Block a user