- #53 Use the full relative path when
npm publish
ing (fixes an issue with npm@7 publishing) (@nilzona)
- Anders Nilsson (@nilzona)
- #45 Drop Node 11 and 13 support. (@rwjblue)
- #44 Make
release-it
a peer dependency (require host project to provide). (@rwjblue) - #43 Drop
release-it@13
support. (@rwjblue)
- Robert Jackson (@rwjblue)
- Robert Jackson (@rwjblue)
- Robert Jackson (@rwjblue)
- #30 Add logging output (primarily for
--dry-run
/--verbose
). (@rwjblue) - #29 Add additionalManifests.versionUpdates option. (@rwjblue)
- Robert Jackson (@rwjblue)
- Robert Jackson (@rwjblue)
- #25 Pass specific package paths to
npm publish
(avoidprocess.chdir
). (@rwjblue) - #24 Ensure new version is updated appropriately in dependencies. (@rwjblue)
- #22 Ensure prompts have access to required information. (@rwjblue)
- Robert Jackson (@rwjblue)
- Robert Jackson (@rwjblue)
- Robert Jackson (@rwjblue)
- Robert Jackson (@rwjblue)
- Steve Calvert (@scalvert)
- #8 Refactor publishing process. (@rwjblue)
- #1 Basic implementation of
bump
andpublish
methods (@scalvert)
- #11 Ensure any cross package dependency versions are updated. (@rwjblue)
- #6 Leverage try/catch when bumping (to bubble unrelated errors) (@rwjblue)
- #2 Fix bug in
resolveWorkspaces
. (@rwjblue)