Repository navigation
The spec-kit pin is 1.2.6 - #105
Merged
Merged
Conversation
Fourteen releases had accumulated since 1.0.10, and taskstoissues is deprecated with removal planned for a future minor release, so the gap only gets harder to cross. None of them changes how a slice is run here. speckit-specify now takes its spec template from resolve-template.sh, which matters only with presets, and we have none; setup-plan.sh now stops when the plan template is missing or empty, where it used to create an empty plan.md. A refresh reverts the templates it did not write, so plan-template.md and tasks-template.md are restored: they carry this repository's constitution gates, the TDD rule and the documentation tasks. Upstream changed neither file between the two tags, and their manifest hashes are unchanged, so the restored copies lose nothing. The refresh also writes allow_symlinks: false and ignores adapter packages under .specify, neither of which affects anything here. Verified: ./mvnw -B verify passes with 234 tests; conventions-sync check, conventions-check, conventions-format, service-conventions-sync check and service-conventions-check pass; on bash 3.2, resolve-template.sh resolves the tailored plan template and create-new-feature.sh --dry-run names 010. Process: Delivery Phase: Implement Track: Code Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Fourteen releases had accumulated since 1.0.10, and taskstoissues is deprecated with removal planned for a future minor release, so the gap only gets harder to cross. None of them changes how a slice is run here. speckit-specify now takes its spec template from resolve-template.sh, which matters only with presets, and we have none; setup-plan.sh now stops when the plan template is missing or empty, where it used to create an empty plan.md.
A refresh reverts the templates it did not write, so plan-template.md and tasks-template.md are restored and do not appear in this diff: they carry this repository's constitution gates, the TDD rule and the documentation tasks. Upstream changed neither file between the two tags, and their manifest hashes are unchanged, so the restored copies lose nothing. The refresh also writes allow_symlinks: false and ignores adapter packages under .specify, neither of which affects anything here.
The installed CLI on the owner's machine moved to 1.2.6 as well, which no diff shows.
Verified: ./mvnw -B verify passes with 234 tests; conventions-sync check, conventions-check, conventions-format, service-conventions-sync check and service-conventions-check pass; on bash 3.2, resolve-template.sh resolves the tailored plan template and create-new-feature.sh --dry-run names 010.
🤖 Generated with Claude Code