-
Notifications
You must be signed in to change notification settings - Fork 0
Release CsoKit 0.6.1 #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,30 +1,64 @@ | ||
| # CsoKit 0.6.0 | ||
| # CsoKit 0.6.1 | ||
|
|
||
| Windows x64 release for PSP ISO and compressed disc-image workflows. | ||
| CsoKit 0.6.1 is a security, reliability, and release-quality update for Windows x64. | ||
|
|
||
| ## Main functions | ||
| ## Main changes | ||
|
|
||
| - Detect and inspect supported containers. | ||
| - Restrict production native-library loading to the application directory. | ||
| - Validate native ABI compatibility before native codecs are used. | ||
| - Improve cancellation for verification, compression, decompression, repair, CLI Ctrl+C, and the desktop Stop action. | ||
| - Prevent incomplete output from replacing the final destination after cancellation or failure. | ||
| - Apply bounded compression-worker limits and safe queue sizing. | ||
| - Add a central Application layer shared by the CLI and desktop interface. | ||
| - Enforce output base names containing 2 to 10 Unicode characters. | ||
| - Improve early CLI validation and JSON failure responses. | ||
| - Strengthen verification and repair handling for supported containers. | ||
| - Repair the standalone published-executable smoke test and include it in the main verification gate. | ||
| - Simplify end-user documentation and remove internal reports. | ||
|
|
||
| ## Supported workflows | ||
|
|
||
| - Detect and inspect ISO, CSO, ZSO, DAX, and supported CSO2 input. | ||
| - Analyze PSP ISO structure. | ||
| - Verify CSO, ZSO, and DAX input. | ||
| - Verify compressed containers, including deep block verification and SHA-256. | ||
| - Compress ISO into CSO1. | ||
| - Decompress CSO into ISO. | ||
| - Rebuild readable input into verified CSO1 output. | ||
| - Produce JSON output for automation. | ||
| - Produce structured JSON output for scripts. | ||
|
|
||
| ## Installation | ||
| ## Recommended usage | ||
|
|
||
| Recommended compression profile: | ||
|
|
||
| .\csokit.exe compress ".\game.iso" --profile game-safe | ||
|
|
||
| Extract the complete release ZIP and keep `csokit.exe` beside `CsoKit.Native.dll`. | ||
| Verify important output before deleting the original image: | ||
|
|
||
| Run: | ||
| .\csokit.exe verify ".\game.cso" --deep --sha256 | ||
|
|
||
| ## Installation | ||
|
|
||
| 1. Download csokit-0.6.1-win-x64.zip. | ||
| 2. Extract the complete archive into one folder. | ||
| 3. Keep csokit.exe beside CsoKit.Native.dll. | ||
| 4. Run: | ||
|
|
||
| .\csokit.exe native-info | ||
| .\csokit.exe --help | ||
|
|
||
| ## Important | ||
| ## Verification | ||
|
|
||
| - Debug build: PASS. | ||
| - Release build: PASS. | ||
| - Automated tests: 201/201 PASS. | ||
| - Native integration: PASS. | ||
| - Published executable smoke: PASS. | ||
| - Native ISO to CSO to ISO round-trip: PASS. | ||
| - Release package verification: PASS. | ||
|
|
||
| ## Important notes | ||
|
|
||
| - `game-safe` is the recommended compression profile. | ||
| - Output base names must contain 2 to 10 Unicode characters. | ||
| - Existing output is not overwritten without `--force`. | ||
| - Repair cannot reconstruct unreadable source data. | ||
| - Verification checks structure, not emulator compatibility. | ||
| - Existing output files are not overwritten unless --force is supplied. | ||
| - Repair cannot recreate unreadable or missing source data. | ||
| - Structural verification does not guarantee emulator or physical-device compatibility. | ||
| - Output base names must contain 2 to 10 Unicode characters; the extension is not counted. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| 0.6.0 | ||
| 0.6.1 |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When users interpret “inspect” as the documented
csokit infoworkflow and supply an ISO, ZSO, or DAX file, this claim is incorrect:InfoCommandpasses every input toCsoHeaderReaderand explicitly documents onlyinfo <input.cso>(src/CsoKit.Cli/Commands/InfoCommand.cs:15-16,160-162), so those formats fail header validation even thoughdetectsupports them. Split this into detection support for all listed formats and inspection support for CSO1/CSO2.Useful? React with 👍 / 👎.