Repository navigation
docs: lockstep probe red — maps 3.0.0 vs gemspec ~/> 2.5 constraint - #427
Merged
Merged
Conversation
…er decision recorded)
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.
Summary
The weekly
lockstep-checkresolve job on interscript-ruby fired red on 2026-11-09 exactly as designed: maps main now carriesINTERSCRIPT_MAPS_VERSION = "3.0.0"(released 2026-11-08) whileinterscript.gemspecstill constrainsinterscript-maps "~> 2.5", so every bundler resolution against the maps path source fails. Same-sha evidence: ruby main 346a957 resolved green 2026-11-08 13:01 UTC, red 2026-11-09 15:07 UTC.Recorded as an OWNER DECISION (dependency contract + release): raise the gemspec constraint as part of the next interscript-ruby release. Until then the weekly probe stays red — that is its function. Also noted: the ts main "Dependabot" check failure is a GitHub dependabot-container infra error (security-update job for minimatch), self-retrying, no action.