Skip to content

fix: support Valkey URL schemes - #74

Merged
mcollina merged 1 commit into
mainfrom
fix/63-valkey-url-schemes
Jul 15, 2026
Merged

mcollina merged 1 commit into
mainfrom
fix/63-valkey-url-schemes

Conversation

@mcollina

Copy link
Copy Markdown
Collaborator

Summary

  • parse valkey:// and valkeys:// database paths like their Redis-compatible equivalents instead of treating them as Unix socket paths
  • enable TLS for valkeys:// while preserving explicit TLS options
  • document the Valkey URL schemes and retained redis:// / rediss:// compatibility
  • add URL parsing, constructor, and TLS transport regression coverage

This also implements the complete URL parsing and test coverage requested by #33.

Validation

  • npm run build
  • npm run lint (passes with the existing warnings)
  • focused unit and TLS tests: 33 passing
  • npm test: 434 passing, including package export and tsd checks
  • Prettier check for the changed test and utility files

Fixes #63

Signed-off-by: Matteo Collina <hello@matteocollina.com>
@mcollina
mcollina merged commit a00dd17 into main Jul 15, 2026
15 checks passed
@mcollina
mcollina deleted the fix/63-valkey-url-schemes branch July 15, 2026 08:56
@melroy89

Copy link
Copy Markdown

Owh hi thank you once again.

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.

Valkey:// protocol?

2 participants