Repository navigation
DEX-2183: warn once at startup and add a README deprecation banner - #347
Merged
Merged
Conversation
…s deprecated The SDK reaches end-of-life on November 1, 2026. The constructor now prints a one-time console warning pointing at @fireblocks/ts-sdk, silenced by setting FIREBLOCKS_SDK_SUPPRESS_DEPRECATION_WARNING, and the README opens with a deprecation banner.
npm deprecate only marks versions that already exist, so a version published after the package is deprecated installs without a warning. This repo publishes through OIDC and deliberately holds no npm token, and OIDC cannot run npm deprecate, so the step after publish raises a warning and puts the exact npm deprecate command in the run summary for a fireblocks-sdk maintainer on npm to run by hand.
mottymilshtein
changed the title
No further releases are planned after this one, and nobody reads the release run's log for it. npm deprecate is run once by hand right after this release.
mottymilshtein
changed the title
YoavBZ
approved these changes
Oct 4, 2026
asafs932
approved these changes
Oct 4, 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
3 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.
What
FireblocksSDKconstructor prints a one-timeconsole.warn: the SDK is deprecated, it reaches end-of-life on November 1, 2026, and users should migrate to@fireblocks/ts-sdk, with the migration guide link. It fires once per process however many clients are created. SettingFIREBLOCKS_SDK_SUPPRESS_DEPRECATION_WARNINGto any value turns it off, for customers with strict log monitoring.@fireblocks/ts-sdk, with the guide link. It's a plain blockquote, not GitHub's> [!IMPORTANT]syntax, because npm doesn't render that syntax and would show the tag as literal text.Not included:
@deprecatedtagsTagging the SDK class
@deprecatedwould cross it out in editors. I left it out on purpose. typescript-eslint'sno-deprecatedrule is an error in thestrict-type-checkedpreset, so customers using that preset would have their lint fail after upgrading. DEX-2183 asks to signal deprecation "without breaking anyone", and it made the runtime warning switchable for the same reason. A lint error has no such switch.After the release (DEX-2185)
Right after this release, a
fireblocks-sdkmaintainer deprecates the package on npm: npmjs.com →fireblocks-sdk→ Settings → Deprecate package. That marks every version, including this one. Message to use:No further releases are planned, so this is a one-time step.
Tested
tscandtslintpass.FIREBLOCKS_SDK_SUPPRESS_DEPRECATION_WARNING=1it didn't appear.🤖 Generated with Claude Code