chore: add changeset for v0.1.0 release#59
Merged
Conversation
Merged
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.
Summary
Adds a changeset to trigger the first functional npm release (v0.1.0).
The currently published
@enbox/memoryd@0.0.1contains only placeholder stubs from the initial scaffolding — the CLI entry point is 149 bytes and does nothing. This is whymemoryd --help,memoryd auth login, and all other commands produce zero output when installed vianpm install -g.What v0.1.0 includes
Verification
Built locally and verified
npm pack --dry-runincludes 192 files (vs 82 in the broken 0.0.1), withdist/esm/cli/main.jsat 8.8KB (vs 149B).