Packages

@google-cloud/vision

6.2.0 · 12 Oct 2026Apache-2.01.1M / weekRepositoryHomepagenpmAtom feed

Upgrading @google-cloud/vision From 0.22.0 to 6.2.0

72 releases in betweennotes for 54

Other targets from 0.22.0Newest 0.x0.25.0
  1. 0.22.0yours
  2. 1 release
  3. 0.23.0major
  4. 0.24.0major
  5. 0.25.0major
  6. 1.0.0major
  7. 17 releases
  8. 2.0.0major
  9. 16 releases
  10. 3.0.0major
  11. 6 releases
  12. 4.0.0major
  13. 10 releases
  14. 5.0.0major
  15. 10 releases
  16. 6.0.0major
  17. 2 releases
  18. 6.2.0target
8+
changes to make
0
advisories fixed
40+
new
36+
fixes

Counted from 54 of 72 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking6.0.0
  • Breaking5.0.0
  • Breaking4.0.0
  • Breaking3.0.0
  • Breaking3.0.0
  • Breaking2.0.0
  • Breaking1.8.0
  • Breaking1.0.0

Release by release

  1. 6.2.0

    12 Oct 20261 new
    • New

      Update API sources and regenerate

  2. 6.1.1

    28 Sep 20261 fix
    • Fixed

      Update package.json and .gitignore across packages

  3. 6.1.0

    8 Sep 20261 new
    • New

      Upgrade librarian gapic-generator-typescript to v5.2.0

  4. 6.0.0

    Migration needed10 Aug 2026
    • Breaking

      Upgrade minimum Node.js version to 22

  5. 5.3.7

    4 Jun 20261 fix
    • Fixed

      deps: Remove vulnerable dependency uuid

  6. 5.3.6

    1 May 20262 fixes
    • Fixed

      Change the copyright year for files in the packages folder

    • Fixed

      Do not publish the protos to npm

  7. 5.3.5nothing new or fixed in the note

  8. 5.3.4

    13 Oct 20251 fix
    • Fixed

      Remove unused GatewayServiceClient

4 other lines we could not sort, mostly version bumps
  • Revert "fix: Do not publish the protos to npm"

    5.3.6
  • ApiError: An API failure, usually from malformed input

    0.23.0
  • SigningError: A signed URL or policy couldn't be created, usually from missing credentials

    0.23.0
  • Switch to let/const

    0.22.1

36 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.