-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare 0.5.0 release #43
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In addition to the comments so far, the PR title says this is preparing a release of 0.6.0, not 0.5.0.
970f58a
to
a94597d
Compare
CHANGELOG.md
Outdated
@@ -8,13 +8,17 @@ Subheadings to categorize changes are `added, changed, deprecated, removed, fixe | |||
|
|||
--> | |||
|
|||
The latest published Vello SVG release is [0.3.1](#031-2024-07-29) which was released on 2024-07-29. | |||
You can find its changes [documented below](#031-2024-07-29). | |||
The latest published Vello SVG release is [0.5.0](#031-2024-07-29) which was released on 2024-11-16. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The first link here still has the wrong target, unfortunately. We link to the same place twice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commit message and PR title still need updating as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this now follows the Linebender standard for this stuff. Thanks.
Doing so now. |
Thanks! |
There was a policy failure in linebender#43 It seems to me that only people who have permission to make releases should merge release PRs
There was a policy failure in #43 It seems to me that only people who have permission to make releases should merge release PRs
No description provided.