chore!: bump version to 3.0.0 — breaking change missed in prior PR#204
Merged
Conversation
pranishnepal
force-pushed
the
follow-up/WAL-1481
branch
2 times, most recently
from
74659a7 to
bb8daf6
Compare
BREAKING CHANGE: All KMS_* environment variables were renamed to KEY_PROVIDER_* in PR #195. Any deployment using the old variable names will break without a config update: KMS_URL -> KEY_PROVIDER_URL KMS_SERVER_CA_CERT_PATH -> KEY_PROVIDER_SERVER_CA_CERT_PATH KMS_CLIENT_TLS_KEY_PATH -> KEY_PROVIDER_CLIENT_TLS_KEY_PATH KMS_CLIENT_TLS_CERT_PATH -> KEY_PROVIDER_CLIENT_TLS_CERT_PATH KMS_CLIENT_TLS_KEY -> KEY_PROVIDER_CLIENT_TLS_KEY KMS_CLIENT_TLS_CERT -> KEY_PROVIDER_CLIENT_TLS_CERT KMS_CLIENT_TLS_CA_CERT -> KEY_PROVIDER_CLIENT_TLS_CA_CERT KMS_SERVER_CERT_ALLOW_SELF_SIGNED -> KEY_PROVIDER_SERVER_CERT_ALLOW_SELF_SIGNED This was missed in the prior semver bump (2.1.0 -> 2.1.1). Correcting to 3.0.0 per semver convention. Ticket: WAL-1481 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
pranishnepal
force-pushed
the
follow-up/WAL-1481
branch
from
bb8daf6 to
a6ea296
Compare
pranishnepal
requested review from
margueriteblair,
pranavjain97 and
rajangarg047
margueriteblair
approved these changes
May 20, 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.
Why
Corrects the version from 2.1.1 to 3.0.0.
Why
PR #195 (refactor: rename KMS to Key Provider) introduced a breaking change that was not reflected in the semver bump at the time:
All KMS_* environment variables were renamed to KEY_PROVIDER_*:
KMS_URL -> KEY_PROVIDER_URL
KMS_SERVER_CA_CERT_PATH -> KEY_PROVIDER_SERVER_CA_CERT_PATH
KMS_CLIENT_TLS_KEY_PATH -> KEY_PROVIDER_CLIENT_TLS_KEY_PATH
KMS_CLIENT_TLS_CERT_PATH -> KEY_PROVIDER_CLIENT_TLS_CERT_PATH
KMS_CLIENT_TLS_KEY -> KEY_PROVIDER_CLIENT_TLS_KEY
KMS_CLIENT_TLS_CERT -> KEY_PROVIDER_CLIENT_TLS_CERT
KMS_CLIENT_TLS_CA_CERT -> KEY_PROVIDER_CLIENT_TLS_CA_CERT
KMS_SERVER_CERT_ALLOW_SELF_SIGNED -> KEY_PROVIDER_SERVER_CERT_ALLOW_SELF_SIGNED
Any deployment using the old KMS_* env vars will break without a config update. Per semver, a breaking change to the public configuration interface requires a major version bump.
We also did an SDK bump at #203