Skip to content

Remove base64 from sig manifest - #852

Merged
sferik merged 1 commit into
httprb:mainfrom
hakanensari:remove-base64-sig-dependency
Aug 25, 2026
Merged

Remove base64 from sig manifest#852
sferik merged 1 commit into
httprb:mainfrom
hakanensari:remove-base64-sig-dependency

Conversation

@lineoffligbot

Copy link
Copy Markdown
Contributor

#778 dropped the runtime dependency on the base64 gem in favor of the vendored HTTP::Base64, but the entry in sig/manifest.yaml was left behind. Because of it, rbs collection warns for consumers whose bundle lacks the base64 gem (the default on Ruby >= 3.4, where base64 is no longer a default gem):

WARN -- rbs: Cannot find `base64` gem. Using incorrect Bundler context?

The signatures define their own HTTP::Base64 module and reference nothing from the real Base64, so the dependency can go. rake steep passes with the entry removed.

Base64 was dropped from the runtime dependency in favor of the vendored
HTTP::Base64. The stale manifest entry causes rbs collection to warn when
the base64 gem is absent, particularly for Ruby >= 3.4 users.
hakanensari pushed a commit to lineofflight/amazon-ads-ruby that referenced this pull request Aug 25, 2026
Http 6 includes RBS signatures, sourcing types from the gem instead of
gem_rbs_collection. Add base64 to ignore list as http 6 declares stale
base64 dependency (httprb/http#852).

@sferik sferik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@sferik
sferik merged commit a210c0a into httprb:main Aug 25, 2026
8 of 9 checks passed
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.

2 participants