Release 0.1.0#30
Merged
Merged
Conversation
Mrtenz
approved these changes
Jun 4, 2026
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
2 participants
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.
First publication of
@metamask/skillsto npm —0.1.0. (Replaces #27, which GitHub auto-closed when its branch was renamed.)What
package.json:0.0.0→0.1.0.CHANGELOG.md: move[Unreleased]entries into[0.1.0].Builds on #29 (reset the premature
0.1.0bump to a0.0.0baseline), so this is the genuine first release at0.1.0.On merge
Squash-merge with subject
Release 0.1.0.is-releasesees0.0.0 → 0.1.0→publish-release.ymlruns → GitHub release/tag, then npm publish (gated by thenpm-publishenvironment).Validation (local)
yarn changelog:validate(normal +--rc) ✓ ·yarn build✓ ·yarn test33/33 ✓ ·yarn pack:dry-run→metamask-skills-0.1.0.tgz✓Note
Tag-prefix follow-up: CHANGELOG/
validate-changelog.shuse--tag-prefix '@metamask/skills@'butaction-publish-release@v3createsv0.1.0tags — npm unaffected, only the changelog release link would 404. Worth aligning tovseparately.