Skip to content

Tighten tls bounds to >= 2.3.0 && < 2.4#2

Merged
jappeace merged 1 commit intojappeace:replace-mem-with-ramfrom
jappeace-sloth:replace-mem-with-ram
Mar 7, 2026
Merged

Tighten tls bounds to >= 2.3.0 && < 2.4#2
jappeace merged 1 commit intojappeace:replace-mem-with-ramfrom
jappeace-sloth:replace-mem-with-ram

Conversation

@jappeace-sloth
Copy link

Summary

  • Update tls dependency bounds from >= 2.1.2 to >= 2.3.0 && < 2.4
  • tls 2.3.0 is the first version using ram instead of memory, so the lower bound ensures type compatibility
  • Tight upper bound for safety

Addresses feedback from @Yuras on snoyberg#573.

🤖 Generated with Claude Code

tls 2.3.0 is the first version using ram instead of memory.
Older tls versions (< 2.3.0) use memory and will cause type errors
when combined with this package which now depends on ram.
The upper bound ensures compatibility with the current tls API.

Prompt: add bounds to the PR such that this branch has a tls with
the ram change already included, but also a tls with a tight upper bound

Tokens used: ~200k

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@jappeace jappeace merged commit 3309953 into jappeace:replace-mem-with-ram Mar 7, 2026
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