chore: loosen base64 dependency to allow 0.3.x#61
Open
erimicel wants to merge 1 commit intotypesense:masterfrom
Open
chore: loosen base64 dependency to allow 0.3.x#61erimicel wants to merge 1 commit intotypesense:masterfrom
erimicel wants to merge 1 commit intotypesense:masterfrom
Conversation
`base64 0.3.0` was released in May 2025 and the API used by this gem (only `Base64.encode64`) is unchanged. The pessimistic constraint `~> 0.2.0` blocks bundler from resolving it, which forces apps that depend on a newer base64 transitively to downgrade or skip this gem. Loosens to `~> 0.2`, which allows 0.2.x and 0.3.x while still capping at 1.0 should the API ever change meaningfully. Closes typesense#50.
tharropoulos
approved these changes
Apr 28, 2026
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
2 participants
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.
Closes #50.
base64 0.3.0shipped in May 2025 and~> 0.2.0intypesense.gemspecblocks bundler from resolving it.The only
Base64API this gem uses isBase64.encode64(lib/typesense/keys.rb:26,29) — that has been stable across everybase64release.Loosens the constraint to
~> 0.2, which allows 0.2.x and 0.3.x while still capping below 1.0 if the API ever changes meaningfully.Verification
bundle update base64resolves tobase64 0.3.0.bundle exec rspec(api_call, configuration, key, keys specs) — all green against 0.3.0.PR Checklist