release: prepare scoped public npm package - #3
Merged
Merged
Conversation
Chumaniac
marked this pull request as ready for review
August 7, 2026 09:25
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.
What changed
@chumaniac/skillsyncbecause the unscopedskillsyncname is already occupied.publishConfig.access: public.Validation
npm run check— 69 test files passed, 1 skipped; 426 tests passed, 1 skipped; type-check, lint, and build passed.npm pack --dry-run— public allowlist inspected successfully.git diff --check— passed.Release prerequisite
Before merging a release tag, configure the npm Trusted Publisher for user
Chumaniac, repositoryskillsync, workflow.github/workflows/release.yml, withnpm publishallowed. The package remains offline-first; live runtime capabilities are still disabled pending independent security and controlled-environment approval.