Repository navigation
Prepare reviewed Base64String 1.3.0 release snapshot and package - #30
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prepare Base64String 1.3.0 from the configured release baseline. Selectively port the reviewed encoding/pipeline fix from PR #28, plus the Windows padding follow-up merged in PR #32 (51b283c). The original 31 regression cases remain, with three additional malformed-padding cases.
The source manifest and out/ both declare 1.3.0. New-ReleaseOutput.ps1 reproducibly generates matching code, manifest, README, icon and license. The owner explicitly confirmed WTFPL: module-local LICENSE, packaged LICENSE and both manifest URLs now agree. The repository-wide BSD license is unchanged. Prior owner license edits were preserved; a3b8551's padding-port commit message was inaccurate (that commit captured license edits), and the actual selective guard port/package regeneration is in 564a30c. No history was rewritten.
The read-only candidate workflow is pinned to automation 4855606. It tests the exact candidate commit on Windows PowerShell 5.1, Windows pwsh, Linux and macOS, validates committed-vs-regenerated hashes, and uploads package/NUnit evidence. It also runs on the final release-branch commit after integration. It has no Gallery credentials and cannot create releases or mutate issues.
Local macOS pwsh 7.7.0/Pester 4.10.1: 34 source and 34 installed-package tests passed. Module, generated and staged WTFPL bytes match (SHA256 6fcb3400cc6126e54b9c5be59bb396fd2ce4cd6d075ec559f0aa4171372307be). Hosted candidate results must pass before integration.
References #29 and #22. Neither issue is completed by this PR. No Gallery upload is authorized or performed. Production release/dry-run dispatch awaits separate automation integration into master via PR #31; master is not changed by this release PR.