Skip to content

Release 0.11.3 #467

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

Merged
merged 5 commits into from
Jul 21, 2025
Merged

Release 0.11.3 #467

merged 5 commits into from
Jul 21, 2025

Conversation

sagudev
Copy link
Contributor

@sagudev sagudev commented Jul 17, 2025

I've triaged all commits up to 08f66e1 and also run release-plz to be sure that we can do non breaking change. For the release date I wrote 2025-07-21.

Copy link
Contributor

@waywardmonkeys waywardmonkeys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see you dated this for tomorrow, which is good ... I think we should talk about this briefly in Office Hours today. I'm on board with this.

If we were doing a minor patch bump then there'd be a lot more difficulty as when we bump to 0.12, there's a lot of other breaking stuff to roll into that release.

@sagudev
Copy link
Contributor Author

sagudev commented Jul 17, 2025

If we were doing a minor patch bump then there'd be a lot more difficulty as when we bump to 0.12, there's a lot of other breaking stuff to roll into that release.

Just curios, which stuff?

@sagudev sagudev force-pushed the 0_11_3 branch 2 times, most recently from 84b4bad to de779dc Compare July 17, 2025 12:01
@sagudev
Copy link
Contributor Author

sagudev commented Jul 17, 2025

rebased and added new changelog entry

@waywardmonkeys
Copy link
Contributor

If we were doing a minor patch bump then there'd be a lot more difficulty as when we bump to 0.12, there's a lot of other breaking stuff to roll into that release.

Just curios, which stuff?

The main thing on my mind is some changes to make doing a C FFI easier, which makes for a bunch of small changes to the enums. Source compatible, but representation size changes.

@sagudev
Copy link
Contributor Author

sagudev commented Jul 18, 2025

Rebased and added #452.

@sagudev sagudev requested a review from waywardmonkeys July 18, 2025 14:54
Copy link
Contributor

@waywardmonkeys waywardmonkeys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but I can't do the release because I'm preparing for extended travel.

@sagudev sagudev mentioned this pull request Jul 18, 2025
Signed-off-by: sagudev <[email protected]>
@sagudev
Copy link
Contributor Author

sagudev commented Jul 18, 2025

Rebased and added #469.

I will leave merging to someone with publish permissions.

Signed-off-by: sagudev <[email protected]>
tomcur added 3 commits July 21, 2025 23:56
GitHub's markdown renderer adds vertical spacing to all bullet list
items if one of them has a paragraph. I don't think there's much we can
do.
@tomcur tomcur added this pull request to the merge queue Jul 21, 2025
Merged via the queue into linebender:main with commit ce236de Jul 21, 2025
15 checks passed
@sagudev sagudev deleted the 0_11_3 branch July 22, 2025 04:08
github-merge-queue bot pushed a commit to linebender/vello that referenced this pull request Jul 22, 2025
github-merge-queue bot pushed a commit to linebender/vello that referenced this pull request Jul 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants