Packages

@smithy/node-config-provider

4.6.2 · 15 Aug 2026Apache-2.056.4M / weekRepositoryHomepagenpmAtom feed

Upgrading @smithy/node-config-provider From 1.0.1 to 4.6.2

103 releases in betweennotes for 102

Other targets from 1.0.1Newest 1.x1.1.0
  1. 1.0.1yours
  2. 3 releases
  3. 2.0.0major
  4. 31 releases
  5. 3.0.0major
  6. 13 releases
  7. 4.0.0major
  8. 52 releases
  9. 4.6.2target
3+
changes to make
0
advisories fixed
12+
new
10+
fixes

Counted from 102 of 103 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking4.0.0
  • Breaking3.0.0
  • Breaking2.0.0

Release by release

  1. 4.6.2

    15 Aug 20261 fix
    • Fixed

      Restore npm provenance attestations. No functional changes.

  2. 4.5.8 – 4.6.111 releases, nothing new or fixed in the notes

  3. 4.5.7

    8 Jul 20261 fix
    • Fixed

      Types updates for isolatedModules=true

  4. 4.5.1 – 4.5.66 releases, nothing new or fixed in the notes

  5. 4.5.0

    15 Jun 20261 new
    • New

      Update dist-cjs output format to use plain require/exports statements

  6. 4.4.7

    12 Jun 20262 fixes
    • Fixed

      Update author URL in package.json to be more specific

    • Fixed

      bcbadbc: Package json updates

  7. 4.4.1 – 4.4.66 releases, nothing new or fixed in the notes

  8. 4.4.0

    8 May 20263 new
    • New

      Consolidate core/retry and related cleanup

    • New

      Consolidation for core/protocols

    • New

      Package consolidation for core/config

102 internal lines (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.