Skip to content

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

Open
ronaldtse wants to merge 1 commit into
mainfrom
chore/ci-maps-gem-fallback
Open

ci: fall back to published interscript-maps gem when ../maps is absent#766
ronaldtse wants to merge 1 commit into
mainfrom
chore/ci-maps-gem-fallback

Conversation

@ronaldtse

@ronaldtseronaldtse commented Aug 22, 2026•
edited
Loading

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)

@ronaldtse
ci: fall back to the published interscript-maps gem when ../maps is a…
d45b65c
…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.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@ronaldtse