{{ message }}
Repository navigation
Refresh the install after git stack update - #44
Merged
Merged
Conversation
Updating swapped the binary but left everything git stack install had set up as it was, so the skill kept describing the old release, aliases a new version adds never showed up and the completion script went stale until you ran install again (and answered its questions). Update now hands over to the new binary once it's in place, which brings whatever install set up before in line with it without prompting; aliases, completion, the MCP registration if the binary moved, and the skills. It only touches what was installed in the first place and only prints what it changed. It has to be the new binary since the completion script and the skill are built into it, so the hidden install --refresh flag it calls has to keep working in every release. While doing this the skill now goes to Codex as well as Claude Code (each only when you have that agent's config directory), and update gets its own spinner for the download and ends on a warning line with next steps when there's a release it didn't install.
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.
Updating swapped the binary but left everything
git stack installhad set up as it was. So the skill kept describing the old release, aliases a new version adds never showed up, and the completion script went stale until you ran install again (and answered its questions again).Now once the new binary is in place, update hands over to it to bring whatever install set up before in line, without prompting: aliases, completion, the MCP registration if the binary moved, and the skills. It only touches what you installed in the first place, leaves an alias you've pointed elsewhere alone, and only prints what it changed (so most of the time you just get the update line). It has to be the new binary doing this since the completion script and the skill are built into it.
While doing this the skill now goes to Codex too (
~/.codex/skills/git-stack, or under$CODEX_HOME), each agent only if you have its config directory. Update also gets its own spinner for the download and ends on a warning line with next steps when there's a release it didn't install, like the rest of the commands.One thing for releases: the new binary is called as
install --refresh(hidden flag), and older binaries will call it on newer ones, so that flag has to keep working. Until this ships,update --forcefrom a dev build lands on v0.3.0, which doesn't have it, so you get an error telling you to rungit stack install(the update itself still happened).