Packages

@unhead/shared

3.4.3 · 13 Oct 2026MIT586.1k / weekRepositoryHomepagenpmAtom feed

Upgrading @unhead/shared From 1.5.5 to 1.11.21

71 releases in betweennotes for 63

Reading releases, release notes and advisories…

Other targets from 1.5.5Latest3.4.3
  1. 1.5.5yours
  2. 12 releases
  3. 1.8.5security
  4. 1.8.6security
  5. 4 releases
  6. 1.8.11breaking
  7. 9 releases
  8. 1.9.0breaking
  9. 41 releases
  10. 1.11.21target
9+
changes to make
0
advisories fixed
15+
new
112+
fixes

Counted from 63 of 71 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking1.9.0
  • Breaking1.9.0
  • Breaking1.9.0
  • Breaking1.9.0
  • Breaking1.9.0
  • Breaking1.8.11
  • Deprecated1.11.0
  • Deprecated1.10.0
  • Deprecated1.7.0

Security

  • Check innerHTML is a string when applying XSS fixes

    1.8.6
  • unhead: XSS prevention on JSON payloads injected at resolve

    1.8.5

Release by release

  1. 1.11.21

    19 Nov 20261 fix
    • Fixed

      v1: Harden useHeadSafe input sanitization

  2. 1.11.16 – 1.11.204 releases, no release note

  3. 1.11.15

    7 Jan 20251 new · 2 fixes
    • New

      Avoid inlining dependencies

    • Fixed

      schemaOrg: Resolve nodes with custom nodes

    • Fixed

      vue2: head() not called with vm context

  4. 1.11.14

    10 Dec 20241 fix
    • Fixed

      useScript: Allow load() to be called again once remove() is called

  5. 1.11.13no release note

  6. 1.11.12

    25 Nov 20243 fixes
    • Fixed

      schema: Prefer ReturnType instead of infer

    • Fixed

      schema-org: Mark unhead as peer dependency

    • Fixed

      schema-org: Duplicate tag generated in some instances

  7. 1.11.11

    1 Nov 20243 fixes
    • Fixed

      Title getting encoded when using titleTemplate

    • Fixed

      schemaOrg: Avoid rendering empty schema graph

    • Fixed

      schemaOrg: Duplicate ReadAction's for WebPage

  8. 1.11.10

    16 Oct 20241 fix
    • Fixed

      addons: Avoid transforming wrong composables

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.