Repository navigation
chore(release): 0.19.0 - #172
Merged
Merged
Conversation
The shared library's name carries the major version (Linux libemberwave_ffi.so.0, macOS @rpath/libemberwave_ffi.0.dylib), which a program that links it from this version on records, so the minor version changes. The release archives hold the versioned file with the unversioned name as a link. Also: wgpu 30.0.2, the notices in the crates on crates.io, a test of the library's export table and of its name, scripts/package_ffi.sh, the 1.0 checklist and decision D75, and the measurements of the display loop, the performance model and Chrome's encoders in BENCHMARKS.md. Version 0.19.0 in Cargo.toml and the C API's version constants, header regenerated, the CHANGELOG entry, the status line and the XCFramework URL. Claude-Session: https://claude.ai/code/session_019fJGoCTvP5e7n599q3ZQ42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Release 0.19.0, 15 days after 0.18.1. What main gained since: the shared library's name carries the major version (a change for programs that link it, hence the minor version), wgpu 30.0.2, the notices in the crates, the export and name tests,
scripts/package_ffi.sh, the 1.0 checklist and D75, and three measurement studies in BENCHMARKS.md.Changes
Cargo.toml(and the lock file), the C API's version constants (0.19.0, 1900) and the regenerated header.What it changes for a client
See the first paragraph of the CHANGELOG entry: programs linked against the shared library from this version on record
libemberwave_ffi.so.0or@rpath/libemberwave_ffi.0.dylib; the archives hold that file and keep the unversioned names as links.Not in this PR
The tag, the release workflow and the crates.io publish are separate steps. The workflow's packaging step changed with the versioned name (
scripts/package_ffi.sh, run by the C example job on every PR), but the workflow itself has not run since.Testing
cargo test -p emberwave-ffi(header, exports, names, the C API);cargo build --workspace --locked; fmt; the CI jobs of this PR.