Skip to content

ci: fall back to published interscript-maps gem when ../maps is absent - #766

Merged
ronaldtse merged 1 commit into
mainfrom
chore/ci-maps-gem-fallback
Sep 28, 2026
Merged

ronaldtse merged 1 commit into
mainfrom
chore/ci-maps-gem-fallback

Conversation

@ronaldtse

@ronaldtse ronaldtse commented Aug 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • CI rake workflow failed on every bundle command: the Gemfile hardcoded interscript-maps as a path dependency on ../maps, which is never checked out in CI (exit 13, 'The path ../maps does not exist')
  • fall back to the published RubyGems interscript-maps gem when the sibling checkout is absent — the same pattern the secryst group already uses

What this fixes vs what remains

  • FIXED: bundling in CI (all jobs now install and run)
  • REMAINING (pre-existing, out of scope here): 23 standardrb lint offenses on main; pycall-based specs fail in CI (PyCall.import_module("regex") — python engine unavailable on the runners)

Test plan

  • bundle/lock succeeds in every matrix job
  • full rake green (needs the pycall + lint debt addressed separately)

…bsent

The rake workflow only checks out this repo, so the hard path
dependency made every bundle command fail with 'The path ../maps does
not exist' (exit 13). Mirrors the existing secryst-group pattern:
local sibling in dev, published gem in CI.
@ronaldtse
ronaldtse merged commit 5822f30 into main Sep 28, 2026
3 of 11 checks passed
@ronaldtse
ronaldtse deleted the chore/ci-maps-gem-fallback branch September 28, 2026 04:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant