Runtime bundled-library drift
Ruby 3.4 base64 default gem bundled library removed require base64 Gemfile dependency
Authentication code fails on a fresh image although development machines still have the gem installed.
Agent Quick Fix
Repair against the current Ruby 3.4 contract, then keep the change narrow and source-backed.
Product: Ruby 3.4
Current-contract area: `base64` undeclared dependency breaks clean deploy
Likely root cause: Authentication code fails on a fresh image although development machines still have the gem installed.
Repair direction: Verifier checks an explicit dependency or supported replacement and a clean install.Symptom
Authentication code fails on a fresh image although development machines still have the gem installed.
Why This Happens
A library was historically part of the default runtime install but is now only bundled/optional, so project dependency files may not mention it.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Ruby 3.4 base64 default gem bundled library removed require base64 Gemfile dependency
site:stdgems.org base64 Ruby 3.4 default gem bundled gem
https://stdgems.org/3.4.0/