Packages

on-headers

1.1.0 · 17 Jul 2025MIT71.2M / weekRepositoryHomepagenpmAtom feed

Upgrading on-headers From 0.0.0 to 1.1.0

4 releases in betweenevery note read

Reading releases, release notes and advisories…

The note of 1.0.0 lists no breaking change or deprecation, which is rare for a major.

Security

Fixes 1 advisory affecting 0.0.0

Release by release

  1. 1.1.0

    Security fix17 Jul 20251 new · 2 fixes
  2. 1.0.2

    22 Feb 20191 fix
    • Fixed

      Fix res.writeHead patch missing return value

  3. 1.0.1

    30 Sep 20151 new
    • New

      Enable strict mode

  4. 1.0.0

    10 Aug 20141 fix
    • Fixed

      Prevent arguments-related de-opt

6 other lines we could not sort, mostly version bumps
  • Migrate CI pipeline to GitHub actions

    1.1.0
  • 👷 add upstream change detection

    1.1.0
  • ✨ add script to update known hashes

    1.1.0
  • 💚 update CI - add newer node versions

    1.1.0
  • Honor res.statusCode change in listener

    1.0.0
  • Move to jshttp orgainzation

    1.0.0

1 internal line (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.