Release v0.3.1 - #360
Conversation
Project.toml 0.3.0 -> 0.3.1; CHANGELOG [Unreleased] -> [0.3.1] - 2026-09-09, regrouped into Fixed (12) and Added (2, including the examples/RustCrateMacroPyO3Only.jl entry that #359 lands once it can require RustCall 0.3.1); compare links updated. Every issue of milestone v0.3.1 is closed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014iJ1dZ7KEebWDjdY7fhPbw
|
Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue. |
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Can't wait for the next one! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
…t_crate at a package's top level A self-contained example package that binds a PyO3-only crate — no RustCall attribute, no `juliacall_macros` dependency — with a single `@rust_crate ... submodule="Bindings"` at the package's top level, so the bindings module is generated while the package is precompiled (#339) instead of written to a file by a `deps/build.jl` as examples/SampleCratePyO3Only.jl does. Same crate shape, the other front door. - examples/RustCrateMacroPyO3Only.jl/: Project.toml (RustCall only, compat `RustCall = "0.3.1"` — the first release whose `@rust_crate` has `submodule=`; 0.3.0 would not define `Bindings`), src, an `rlib` crate with a mandatory pyo3 (the wrapper links libpython), 37 tests, README. - .github/workflows/Examples.yml: the package in the matrix. - examples/README.md: the example listed. Its CHANGELOG entry landed with the v0.3.1 release (#360), which had to precede this so the compat bound resolves against the checkout. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014iJ1dZ7KEebWDjdY7fhPbw
Closes out milestone v0.3.1: every issue on it is closed (#339, #342, #343, #346, #347, #348, #349, #350, #357).
Project.toml:0.3.0→0.3.1.CHANGELOG.md:[Unreleased]becomes[0.3.1] - 2026-09-09, regrouped into Fixed (12 entries — the review rounds had left three### Fixedentries under### Added) and Added (@rust_crate ... submodule="Bindings", and theexamples/RustCrateMacroPyO3Only.jlexample); compare links updated.Why the example's entry is here before #359 merges. The example's
[compat]has to requireRustCall = "0.3.1"— 0.3.0's@rust_cratehas nosubmodule=, so a registered-package user on 0.3.0 would fail atusing .Bindings(Codex on #359). A0.3.1lower bound cannot resolve against this checkout until this bump lands, so this PR carries the version and the CHANGELOG entry, #359 rebases onto it with the bound and without the CHANGELOG hunk, and@JuliaRegistrator registeris posted only after both are onmain, so the tag contains the example.Verified locally on the release branch:
scripts/lint_*.sh, the docs build, and the fullPkg.test()are green.🤖 Generated with Claude Code
https://claude.ai/code/session_014iJ1dZ7KEebWDjdY7fhPbw