chore(pins): bump rune-mcp to v0.1.0-alpha.4#161
Merged
jh-lee-cryptolab merged 1 commit intoJun 8, 2026
Merged
Conversation
Picks up the /rune:activate fix from CryptoLabInc/rune-mcp#12 (clear the user_deactivated marker so /rune:activate resumes a deactivated daemon). DO NOT MERGE until rune-mcp v0.1.0-alpha.4 is released — the rune release workflow verifies pinned downstream releases exist (gh release view) and will fail otherwise. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
esifea
approved these changes
Jun 8, 2026
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.
Bumps
rune_mcp_versionin.release-pins.yaml:v0.1.0-alpha.3→v0.1.0-alpha.4.Picks up the
/rune:activateresume fix from CryptoLabInc/rune-mcp#12 —/rune:deactivatepersistsuser_deactivatedtoconfig.json, butActivate()never cleared it, so/rune:activatewas a no-op and the daemon stayed dormant untilconfig.jsonwas hand-edited. alpha.4 will be the first release containing that fix.The rune release workflow's "Verify pinned releases existency" step runs
gh release view v0.1.0-alpha.4 --repo CryptoLabInc/rune-mcp. Until that release exists this pin is dangling and tagging rune would fail the release job. Sequence:v0.1.0-alpha.4.Kept as a draft for that reason.
runed_versionis unchanged.