Repository navigation
chore(main): release skillx-sh 0.6.0 - #106
Merged
mrgoonie merged 1 commit intoOct 21, 2026
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main--components--skillx-sh
branch
2 times, most recently
from
October 20, 2026 02:56
e1fd83d to
42c15c5
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--skillx-sh
branch
from
October 20, 2026 03:05
42c15c5 to
640a61a
Compare
Contributor
Author
|
🤖 Created releases: 🌻 |
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.
🤖 I have created a release beep boop
0.6.0 (2026-10-20)
⚠ BREAKING CHANGES
skillx release publish --json(now an alias ofskillx publish <dir>) prints the{"ok": true, "data": {...}}/{"ok": false, "error": {...}}envelope instead of the bare release object, and failures use the documented exit codes instead of always 1. Read the release from.data.Features
Bug Fixes
This PR was generated with Release Please. See documentation.