Feat/engine incompatible dev dependency detection - #71
Merged
pboling merged 296 commits intoOct 4, 2026
Merged
Conversation
The typed-core job installs the candidate psych-merge into an isolated gem home, but a release-bumped checkout pins siblings (ast-merge, tree_haver, yaml-merge) to exact versions the registry does not have yet, so the provider install aborts and the release gate fails. Package the provider's runtime-dependency closure from the candidate root into kernel/tmp/psych-provider-support and pass --provider-support-dir to the kernel gate, which validates the closure and stages it into the disposable gem home before installing the provider. Third-party dependencies still resolve from the registry. Depends on the kernel gate's --provider-support-dir support (structuredmerge/structuredmerge f945cda), already on kernel main. Verified locally: real gate run against the actual 7.1.10 provider plus its sibling closure exits 0 with all sub-suites green; the 11 Ruby workflow structural tests pass and actionlint is clean.
The branch bumped kettle-jem to 7.1.29 without raising the static self-dependency floor in TEMPLATE_MANAGED_DEPENDENCIES, so path-mode reconciliation emitted >= 7.1.28 while the specs assert convergence to the running version (>= 7.1.29). Fails the gem-suite release gate in local-path CI mode; the deps-floor tool only manages external floors, so the self-floor is hand-synced per its introduction.
Bumping TEMPLATE_MANAGED_DEPENDENCIES to 7.1.29 was wrong: the static floor must track the last released version (7.1.28), because path-mode reconciliation preserves it in destination gemfiles and depending on an unpublished version breaks released installs (c743d02). The real defect is that prepare_task_spec.rb:354 and appraisals_and_gemfile_template_spec.rb:1609 assert running-version convergence (non-path mode) while reading ambient ENV. CI's gem-suite job sets STRUCTUREDMERGE_DEV at job level, flipping them into path mode where the released floor is correct behavior. The divergence only appeared when the branch bumped kettle-jem to 7.1.29 (on main version == floor, so both modes agree). Pin both specs to their intended non-path environment.
prepare_task_spec.rb:354 and appraisals_and_gemfile_template_spec.rb:1609 assert convergence to the running version (non-path mode) but read ambient ENV. The CI gem-suite sets STRUCTUREDMERGE_DEV at job level, flipping them into path mode where the released floor is correct. The divergence only appeared once the branch bumped kettle-jem to 7.1.29 (on main version == floor, so both modes agreed). stub_env pins each spec to the non-path mode it documents.
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.
No description provided.