chore(release): 2.0.0#84
Merged
Merged
Conversation
Signed-off-by: yuriyryabikov <22548029+kurok@users.noreply.github.com>
Contributor
Author
|
Please check diffs between releases |
The 2.0 refactor narrowed the "config" peerDependency from ">=1 <4"
(as published in 1.0.1) to "^3.3.12". This was an unintended tightening
— likely from "npm install config" pinning the caret of the then-latest
version — and causes ERESOLVE for consumers still on config@1.x/2.x.
VaultNodeConfig only uses require('config'), config.util.initParam() and
object mutation, all available since config@1, so there is no functional
reason to require v3. Restore the published ">=1 <4" range.
Signed-off-by: Yuriy R <22548029+kurok@users.noreply.github.com>
m2broth
approved these changes
Jun 16, 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.
Release 2.0.0
Cuts a new release off
master. Last published release was v1.0.1 (2024-06-07). This is a major bump becausemastercontains breaking changes (see CHANGELOG).Changes in this PR
package.json:1.0.1→2.0.0package-lock.json: root +packages[""]version →2.0.0CHANGELOG.md: convert# Unreleased→# 2.0.0. Release notes (2026-06-12)Changelog (highlights since v1.0.1)
fetch.request/request-promisewith Node's nativefetch(removes therequestruntime dependency). Closes fix(deps): replace request with native fetch to clear Dependabot alerts #59.api.requestOptions, shallow-merged into everyfetch()call (proxy/SOCKS agent, self-signed/internal-CA via undicidispatcher). Closes add config an http agent #37, RequestError: Error: self signed certificate in certificate chain #29.VaultClient#close()/VaultBaseAuth#cancelTokenRefresh();VaultClient.clear()now closes removed instances. Closes Blinking input cursor after running read #31.regionconfig; STSGetCallerIdentitysigned against the regional endpoint, fixingSignatureDoesNotMatchon non-us-east-1. Closes With IAM Authentication not able to pass region #25.expire_time(RFC3339), falling back tottl. Closes Token expiry derived from creation_time + ttl instead of the documented expire_time #51.AuthTokenExpiredErrorfor expired non-refreshable tokens instead of using a stale token. Closes Unreachable AuthTokenExpiredError: expired non-refreshable tokens are returned instead of raising #50.new Buffer()withBuffer.from()in IAM STS body encoding. Closes Deprecated new Buffer() in VaultIAMAuth (DEP0005) #52.Full details in
CHANGELOG.md.Notes