Repository navigation
Conversation
The agent-context extension that Spec Kit 1.2 ships contains Python that does not follow the project's rules. `.specify` is in the ruff and ty exclude lists. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deploying infrahub-sdk-python with
|
| Latest commit: |
db1ddea
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://58d65636.infrahub-sdk-python.pages.dev |
| Branch Preview URL: | https://pmi-speckit-1-2-upgrade.infrahub-sdk-python.pages.dev |
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## stable #1490 +/- ##
==========================================
- Coverage 85.18% 85.18% -0.01%
==========================================
Files 148 148
Lines 13368 13347 -21
Branches 1975 1965 -10
==========================================
- Hits 11388 11370 -18
+ Misses 1412 1411 -1
+ Partials 568 566 -2
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Follows the "Upgrading spec-kit to 1.2 or later" steps of opsmill-speckit v1.4.1, as in opsmill/infrahub#11376: - remove the review extension, which does not install on Spec Kit 1.x - upgrade the Claude integration to Spec Kit 1.2.5 - reinstall opsmill from the v1.4.1 tag - add the checkpoint extension and the critique-opsmill preset - replace the infrahub Jira preset with jira-branch, and delete dev/spec-kit/presets/infrahub - update agent-context to 1.0.2, the version Spec Kit 1.2.5 ships, and keep its CLAUDE.md configuration No file that the integration manages had local changes, so the forced upgrade loses nothing. Also deletes the command files that Spec Kit 0.x generated in .agents/commands. Spec Kit 1.2 uses the skills in .agents/skills instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…on's The infrahub extension, added in #979, ran speckit.infrahub.feature before each specification to check the Jira reference in the branch name. Its command file was removed with the infrahub preset, so the hook pointed to a command that no longer exists. The jira-branch preset now does that check in speckit.git.feature, so the hook is the git extension's, as in opsmill/infrahub#11376. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The upgrade installs presets in .specify/presets, which rumdl checked, unlike .specify/extensions and .specify/templates. Spec Kit regenerates these files on each upgrade. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The plan, tasks and template scripts of Spec Kit 1.2 need PyYAML, which the system python3 often lacks. The Claude Code and Codex hooks that opsmill-speckit 1.4.1 ships point them at the project environment when it has PyYAML, and do nothing otherwise. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X9ZEsTmHy1shuNRt88HiUb
polmichel
force-pushed
the
pmi-speckit-1.2-upgrade
branch
from
November 8, 2026 18:39
cb368c6 to
db1ddea
Compare
polmichel
changed the title
polmichel
marked this pull request as ready for review
November 9, 2026 13:40
Contributor
|
This PR has 10,953 reviewable changed lines after ignored/generated files are excluded, above this repository's 10,000-changed-line automatic review limit. Most of the diff comes from:
Comment |
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.
Upgrades Spec Kit from 0.11.9 to 1.2.5 and opsmill-speckit from 1.1.0 to 1.4.1, with the same steps as opsmill/infrahub#11376. Part of opsmill/opsmill-speckit#29.
Changes
/speckit-opsmill-autoreplaces/speckit.opsmill.auto.reviewextension is removed, because it does not install on Spec Kit 1.x.checkpointextension and thecritique-opsmillpreset are added.jira-branchpreset replaces theinfrahubpreset.After the merge
pr-review-toolkitClaude Code plugin for a full review. Without it, the review step uses/code-review.specifyCLI to 1.2.5.Tests
Run in clean clones of this branch:
/speckit-opsmill-autocompleted every phase on a sample feature, with a systempython3that has no PyYAML..git.setup-plan.shfor Codex.Review
Review commit by commit. Spec Kit generated most of the upgrade commit.
🤖 Generated with Claude Code