Skip to content

Conversation

@madsmtm
Copy link
Member

@madsmtm madsmtm commented Nov 23, 2025

Changes:

  • Added support for Android using the ndk crate.
  • Added support for wasm64-* targets.
  • Improved examples.
  • Added Buffer::width() and Buffer::height() getters.
  • Context now implements Clone.
  • Context, Surface and Buffer now implement Debug.
  • Bump MSRV to Rust 1.71.
  • Replace log with tracing.
  • Remove cfg_aliases dependency.
  • Update to objc2 0.6, objc2-* 0.3, drm 0.14, rustix 1.0 and windows-sys 0.61.

@madsmtm madsmtm requested review from MarijnS95 and notgull November 23, 2025 13:29
@madsmtm madsmtm force-pushed the madsmtm/new-release branch from 2b49156 to 1ce609d Compare December 13, 2025 20:21
@madsmtm madsmtm merged commit 21e85e9 into master Dec 13, 2025
40 checks passed
@madsmtm madsmtm deleted the madsmtm/new-release branch December 13, 2025 20:31
@madsmtm
Copy link
Member Author

madsmtm commented Dec 13, 2025

Weird, the GitHub release says that notgull released it, do you know why that is?

https://github.com/rust-windowing/softbuffer/releases/tag/v0.4.7

@MarijnS95
Copy link
Member

Weird, the GitHub release says that notgull released it, do you know why that is?

Most likely the release token and crates.io token are set up by him; allowing the CI to publish in his name?

You seem to have preempted that for the crates.io release, which is why CI failed the publish.

Perhaps there is a default GitHub token or thing that allows "GitHub Actions" to post the tag in some nameless way instead - or based on the merger of the release PR?

For crates.io I prefer us to switch to trusted publishing: https://crates.io/docs/trusted-publishing

@madsmtm
Copy link
Member Author

madsmtm commented Dec 14, 2025

Weird, the GitHub release says that notgull released it, do you know why that is?

Most likely the release token and crates.io token are set up by him; allowing the CI to publish in his name?

You seem to have preempted that for the crates.io release, which is why CI failed the publish.

Ooops, I wasn't aware that this repo had releases set up in GH actions. That's probably it then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants