v3.0.0

3.0.0 (2017-12-13)

Bug Fixes

• refactor source to fix a small issue and increase readability (da477e5)
• we don't actually need an npm plugin (for now) (af1470b)

BREAKING CHANGES

• The semantic-release-monorepo/npm plugin is no longer provided.

v2.0.7

2.0.7 (2017-12-12)

Bug Fixes

• get-last-release: don't crash if last release isn't found (3defc79)
• commit files path filter should match beginning of paths (2eed430)

v2.0.6

2.0.6 (2017-12-07)

Bug Fixes

• write getLastRelease plugin to work around missing gitHead (244792f)

v2.0.5

2.0.5 (2017-12-07)

Bug Fixes

• broken imports of npm/github publish (003d309)

v2.0.4

2.0.4 (2017-12-07)

Bug Fixes

• must wrap npm & github publish plugins individually (918b4a1)

v2.0.3

2.0.3 (2017-12-07)

Bug Fixes

• exporting publish as an array doesn't work (4a43737)

v2.0.2

2.0.2 (2017-12-06)

Bug Fixes

• forgot to include npm publish (da720ce)

v2.0.1

2.0.1 (2017-12-01)

Bug Fixes

• use <pkg-name>-<version> for git tag and release notes (1fb040f)

v2.0.0

2.0.0 (2017-11-30)

Features

• refactor plugin to use main repo's plugin structure (6de2c46)
• replace get-commits-plugin branch with 11.0.0 (f5c6065)

BREAKING CHANGES

• Use standard plugins instead of proposed getCommits plugin.

The previous plugin implementation was based around a proposed,
but rejected getCommits plugin.

The new implementation is functionally equivalent, but is slower as it
has to repeat the filtering of commits an additional time. Rather than
doing it once, as in the proposed getCommits, we need to do it for
both analyzeCommits and generateNotes separately. Could probably be
optimized through memoization or global variable.

v1.0.0

1.0.0 (2017-11-25)

Features

• first versions of get-commits and publish plugins (2dc9711)