[TASK] Prepare the 8.5.0 release #419
Conversation
|
I think I see now where the confusion comes from. :sli I created the 8.4.0 release (or better, the 8.4.0 release documentation on GitHub) yesterday because it was missing. Version 8.4.0 had actually been released (i.e., git-tagged, which is what is relevant for Packagist/Composer) on December 11th. You can list the commits since the 8.4.0 tag with this command: git log 8.4.0..HEADI've done my best to make sense of the commits and compile them into the changelog. (For the future, I'd like us to directly add the changelog entries together with their corresponding PRs.) |
|
Oh, and the 8.4.0 released was tagged from this repo's default branch, i.e., |
There was a problem hiding this comment.
Version 8.4.0 had actually been released (i.e., git-tagged, which is what is relevant for Packagist/Composer) on December 11th.
Ah. I see now.
Oh, and the 8.4.0 released was tagged from this repo's default branch, i.e.,
master, I think.
I've gone through the commits since 8.4.0 and believe I've found 3 more fixes and one additional feature. I've also found the PR numbers for the items you added to the changelog without one. The other items you added seem correct.
Given there has actually been one new feature since 8.4.0 (#384), should the next release in fact be 8.5.0?
CHANGELOG.md
Outdated
|
|
||
| - Retain CSSList and Rule comments when rendering CSS (#351) | ||
| - Replace invalid `turns` unit with `turn` (#350) | ||
| - Also allow string values for rules |
There was a problem hiding this comment.
Allowing string values for rules had PR number #348.
CHANGELOG.md
Outdated
| ### Fixed | ||
|
|
||
| - Retain CSSList and Rule comments when rendering CSS (#351) | ||
| - Replace invalid `turns` unit with `turn` (#350) | ||
| - Also allow string values for rules |
CHANGELOG.md
Outdated
| ### Added | ||
|
|
||
| - Add more unit tests |
CHANGELOG.md
Outdated
|
|
||
| ### Added | ||
|
|
||
| - Add more unit tests |
oliverklee
changed the title
I have compiled the changes that seemed relevant from the git history.
oliverklee
force-pushed
the
task/release
branch
from
8e98b2c
to
6d4c502
Compare
|
Done and repushed. |
|
Auto-deletion of merged branches appears not to be enabled. |
|
Also, I didn't see the 'Squash-and-Merge' option, 'Merge Branch' was the default, but maybe I should have looked for a dropdown on the button to change it - can't remember now if there was one. |
|
@JakeQZ @oliverklee thank you both so much! |
|
I've just tagged and released the new version: https://github.com/sabberworm/PHP-CSS-Parser/releases/tag/8.5.0 |
I have compiled the changes that seemed relevant from the git history.