Packages

conventional-commits-parser

7.1.4 · 1 Nov 2026MIT26.3M / weekRepositoryHomepagenpmAtom feed

Upgrading conventional-commits-parser From 0.0.11 to 7.1.4

59 releases in betweennotes for 6

Other targets from 0.0.11Newest 0.x0.2.0
7.0.0, 6.0.0, 5.0.0, 4.0.0, 3.0.0, 2.0.0, 1.0.0 have no release note on GitHub or in the repository's changelog, so their breaking changes are missing from the counts below.
  1. 0.0.11yours
  2. 8 releases
  3. 0.1.0major
  4. 2 releases
  5. 0.2.0major
  6. 1.0.0major
  7. 7 releases
  8. 2.0.0major
  9. 9 releases
  10. 3.0.0major
  11. 11 releases
  12. 3.2.3security
  13. 1 release
  14. 4.0.0major
  15. 5.0.0major
  16. 6.0.0major
  17. 5 releases
  18. 7.0.0major
  19. 5 releases
  20. 7.1.4target
1+
change to make
0
advisories fixed
?
new
6+
fixes

Counted from 6 of 59 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • breaking3.2.4

Security

  • Address ReDoS issue

    3.2.3

Release by release

  1. 7.1.4

    1 Nov 20263 fixes
    • fixed

      Avoid mid-word and non-numeric issue refs (#1571) (dfa8b2d), closes #1570

    • fixed

      Parse references outside of reference action sentences (#1573) (f952155), closes #1564

    • fixed

      Scan lines for references in linear time

  2. 7.1.3

    5 Oct 20262 fixes
    • fixed

      Match reference actions as whole words

    • fixed

      Parse reference actions of footers followed by a colon

  3. 4.0.0 – 7.1.213 releases, no release note

  4. 3.2.4

    Migration needed29 Dec 2021
    • breaking

      Support BREAKING-CHANGE alongside BREAKING CHANGE

  5. 3.2.3

    Security fix24 Oct 2021
    • security

      Address ReDoS issue

  6. 1.3.0 – 3.2.223 releases, nothing new or fixed; 22 without a note

  7. 1.2.3

    6 Aug 20161 fix
    • fixed

      regex: do not treat it as note if there are texts after keywords

  8. 0.0.12 – 1.2.218 releases, no release note

1 internal line (docs, tests, tooling) left out.