Repository navigation
release: prepare SkillSync 0.2.0 installable archive - #24
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
1 participant
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 the GitHub-distributed 0.2.0 CLI archive with exact citation digest/revision binding, privacy-safe HTML review and the existing read-only verification workflow. Update package/CLI/report version expectations and concrete checksummed archive installation links; retain npm registry0.1.0 and all prior releases.
Validation: 643 tests passed,1 existing opt-in Docker test skipped; types,lint,build and package dry-run passed. Initial failures were stale0.1.7 version expectations in reports/docs, updated to0.2.0 without changing functional/security assertions. Changed local Markdown targets and whitespace passed. No new external dependency versions, live provider calls or credential access.
After normal main gates, create the fresh immutable v0.2.0 tag, use the existing verified-main release workflow, download/check provenance and install the published archive into an isolated prefix for the full actual CLI/report journey. Publishing is explicitly authorized by the user's direct-use release request.