Skip to content

fix: drop git-source lutaml-model from Gemfile#29

Open
ronaldtse wants to merge 1 commit into
mainfrom
fix/remove-git-source-gemfile-deps
Open

fix: drop git-source lutaml-model from Gemfile#29
ronaldtse wants to merge 1 commit into
mainfrom
fix/remove-git-source-gemfile-deps

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Summary

  • Remove gem "lutaml-model", github: ..., branch: "..." override from Gemfile
  • Lets bundle install resolve lutaml-model ~> 0.8.0 (already in unitsdb.gemspec) from RubyGems
  • Verified: bundle exec rake spec → 811 examples, 0 failures; resolves to lutaml-model 0.8.16

Why

A release gem must not carry gem "X", github: "..." in its Gemfile: the
release CI workflow (metanorma/ci/.github/workflows/rubygems-release.yml)
deletes Gemfile.lock and re-resolves dependencies with bundle install,
which cannot reliably materialize git-source deps without bundler-specific
workarounds.

lutaml-model 0.8.16 is already published on RubyGems, so the override is
unnecessary and the existing gemspec constraint is sufficient.

Test plan

  • bundle install resolves cleanly to RubyGems-only deps
  • bundle exec rake spec passes (811/811)
  • CI on this PR (rake workflow) passes

Release gems must not depend on git sources. The Gemfile override
points at lutaml-model main on GitHub, but lutaml-model 0.8.16 is
already published on RubyGems and the gemspec already declares
lutaml-model ~> 0.8.0. Removing the override lets Bundler resolve
to the published gem.

Verified locally: bundle install resolves to lutaml-model 0.8.16
from RubyGems, and bundle exec rake spec passes (811 examples, 0
failures).
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