Update CHANGELOG in preparation for 2.2.0 release #228
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Includes the changes in
master
that we'll release in2.2.0
, andthe ones that we can't because of breaking changes, which we'll release
in
3.0.0
I'm proposing to release a new version with the bug fixes and backwards-compatible improvements we've introduced (which we should have released ages ago, but life), including the not-yet-merged fix to
with_labels
in #227.Since
master
has many non-releasable changes, I've created branchv2.2_release
, which forks off of2.1.0
and has the relevant commits cherry-picked into it.Comparison between 2.2.0 (cherry-picked commits) vs 2.1.0
Once we finish the changes to PushGateway, we'll release v3.0 with what's in
master
right now.NOTE: Do not merge this yet. If @Sinjo agrees with this approach, I'll update this README with the correct, date, merge, and add a new release tag in the
v2.2_release
branch