Bump moq-ffi version to 0.1.5

[kixelated]

Summary

This PR bumps the version of the moq-ffi crate from 0.1.4 to 0.1.5 in preparation for a new release.

Changes

• Updated Cargo.toml version field from 0.1.4 to 0.1.5

This is a routine version bump for the FFI bindings crate.

https://claude.ai/code/session_011Kue579CeMf3CLMkSTny4K

[coderabbitai]

Walkthrough

The pull request updates the version number of the moq-ffi crate in rs/moq-ffi/Cargo.toml from 0.1.4 to 0.1.5. This is a minor version increment with no modifications to functional code, configuration settings, or public API signatures. The change consists of a single line modification to the version field in the manifest file.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Bump moq-ffi version to 0.1.5' directly and clearly describes the main change—updating the crate version in Cargo.toml.
Description check	✅ Passed	The description is relevant to the changeset, explaining the version bump from 0.1.4 to 0.1.5 and its purpose as preparation for a new release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/bump-moq-ffi-version-BTlbs

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch claude/bump-moq-ffi-version-BTlbs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@rs/moq-ffi/Cargo.toml`:
- Line 8: Update rs/moq-ffi/CHANGELOG.md to add a new top section for version
0.1.5 matching the Cargo.toml bump: create a heading for "0.1.5" with the
release date (today's release date) and include the patch release notes
summarizing the changes in this release (e.g., bug fixes, minor improvements or
fixes referenced by this PR). Ensure the new entry appears above the existing
0.1.4 entry and follows the same formatting style used in the file.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: add5d87f-fd76-426f-94d8-2482dcbd1a73

📥 Commits

Reviewing files that changed from the base of the PR and between 17554ff and a13e0e8.

📒 Files selected for processing (1)

• rs/moq-ffi/Cargo.toml

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Check for stale references to version 0.1.4 and verify CHANGELOG exists

# Check for any remaining references to the old version
echo "=== Checking for stale version references ==="
rg -n "0\.1\.4" --type toml --type md --type txt

# Check if CHANGELOG exists and mentions the new version
echo -e "\n=== Checking for CHANGELOG ==="
fd -t f "CHANGELOG|CHANGES|HISTORY" --exec echo "Found: {}"

# Check if other workspace members depend on moq-ffi
echo -e "\n=== Checking workspace dependencies on moq-ffi ==="
rg -n "moq-ffi.*version" --type toml

Repository: moq-dev/moq

Length of output: 1386

---

Update CHANGELOG.md with version 0.1.5 entry.

The version bump in Cargo.toml is correctly formatted, but rs/moq-ffi/CHANGELOG.md has not been updated. The latest entry still shows version 0.1.4 (dated 2026-03-18). Add a new section for version 0.1.5 with the release notes for this patch version.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@rs/moq-ffi/Cargo.toml` at line 8, Update rs/moq-ffi/CHANGELOG.md to add a new
top section for version 0.1.5 matching the Cargo.toml bump: create a heading for
"0.1.5" with the release date (today's release date) and include the patch
release notes summarizing the changes in this release (e.g., bug fixes, minor
improvements or fixes referenced by this PR). Ensure the new entry appears above
the existing 0.1.4 entry and follows the same formatting style used in the file.