⚠️ No Changeset found

Latest commit: b133abe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.02%. Comparing base (400ab7b) to head (b133abe).
Report is 1 commits behind head on main.

@@           Coverage Diff           @@
##             main    #1457   +/-   ##
=======================================
  Coverage   81.02%   81.02%           
=======================================
  Files          54       54           
  Lines        2213     2213           
  Branches      658      658           
=======================================
  Hits         1793     1793           
  Misses        416      416           
  Partials        4        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

This package has no changelog 😅 how can I double-check that this won't break anything? Can you identify reasons behind each major bump since v1?

They're just bumping version numbers willy-nilly:
2.0 was typescript upgrade: RienNeVaPlus/human-id@1ad2c86
3.0 changed nothing of note
4.0 removed the jsnext:main field: RienNeVaPlus/human-id@81dd626

Could you resolve the conflict?