Release 66.0.0 #1488
Release 66.0.0 #1488
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
| @@ -6,6 +6,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 | |||
|
|
|||
| ## [Unreleased] | |||
|
|
|||
| ## [6.1.0] | |||
There was a problem hiding this comment.
What do we think about using 6.0.1 instead of 6.1.0? It seems like this bump is a general upgrade and doesn't enable any explicit features, but I could be wrong.
There was a problem hiding this comment.
Hmm. I could see it either way. A dependency bump certainly isn't a bug fix - I could see someone updating to get it, similar to how one might update to get a feature. It's kindof a feature for us actually, since it helps reduce the extension bundle size.
There was a problem hiding this comment.
This official answer seems ambiguous to me: https://semver.org/#what-should-i-do-if-i-update-my-own-dependencies-without-changing-the-public-api
There was a problem hiding this comment.
Hmm, okay. I'll stick with it, then.
| @@ -6,6 +6,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 | |||
|
|
|||
| ## [Unreleased] | |||
|
|
|||
| ## [7.1.0] | |||
There was a problem hiding this comment.
Similar as above — what do we think about 7.0.3?
Co-authored-by: Elliot Winkler <[email protected]>
Co-authored-by: Elliot Winkler <[email protected]>
Explanation
References
#1483
See changelogs
Checklist