Packages

@octokit/core

7.0.8 · 30 Aug 2026MIT50.2M / weekRepositoryHomepagenpmAtom feed

Upgrading @octokit/core From 3.3.2 to 7.0.8

42 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 3.3.2Newest 3.x3.6.0
  1. 3.3.2yours
  2. 3 releases
  3. 3.6.0security
  4. 4.0.0major
  5. 11 releases
  6. 5.0.0major
  7. 7 releases
  8. 6.0.0major
  9. 5 releases
  10. 6.1.4security
  11. 2 releases
  12. 7.0.0major
  13. 7 releases
  14. 7.0.8target

Before you upgrade

Tick each one off as you go
  • Breaking7.0.0
  • Breaking7.0.0
  • Breaking6.0.0
  • Breaking6.0.0
  • Breaking5.0.0
  • Breaking5.0.0
  • Breaking5.0.0
  • Breaking4.0.0

Security

  • deps: bump Octokit dependencies vulnerable to ReDos

    6.1.4
  • deps: Update @octokit/request to ^5.6.3 to address CVE-2022-0235

    3.6.0

Release by release

  1. 7.0.6 – 7.0.83 releases, nothing new or fixed in the notes

  2. 7.0.5

    29 Sep 20251 fix
    • Fixed

      deps: update octokit dependencies, and @sinonjs/fake-timers

  3. 7.0.4nothing new or fixed in the note

  4. 7.0.3

    10 Jul 20251 new
    • New

      Add createLogger to ensure that pino does not break

  5. 7.0.2

    20 May 20251 fix
    • Fixed

      deps: update octokit monorepo (major)

  6. 7.0.1nothing new or fixed in the note

  7. 7.0.0

    Migration needed20 May 20251 fix
    • Breaking

      Drop support for NodeJS v18

    • Breaking

      Set minimal node version in build script to v20

    • Fixed

      Stop testing against NodeJS v18

  8. 6.1.5 – 6.1.62 releases, nothing new or fixed in the notes

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