Repository navigation
Release v0.2.1 - #71
Conversation
WalkthroughThe PR records version 0.2.1 in the changelog, CMake metadata, and ESP-IDF component metadata. The changelog lists security, build, CI, testing, dependency, and documentation changes. Changes0.2.1 Release
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CMakeLists.txt`:
- Line 62: Update the version declaration in build.zig.zon from 0.2.0 to 0.2.1
so it matches the project version in CMakeLists.txt, pkg-config metadata, and
idf_component.yml.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 126018a2-a13d-4890-bd65-350c06798196
📒 Files selected for processing (3)
CHANGELOG.mdCMakeLists.txtidf_component.yml
| endif() | ||
|
|
||
| project(libnostr-c VERSION 0.2.0 LANGUAGES C) | ||
| project(libnostr-c VERSION 0.2.1 LANGUAGES C) |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Synchronize the Zig package version before releasing 0.2.1.
CMakeLists.txt, pkg-config metadata, and idf_component.yml report 0.2.1, but build.zig.zon still declares 0.2.0. Update build.zig.zon so all release metadata identifies the same version.
Proposed fix
- .version = "0.2.0",
+ .version = "0.2.1",🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CMakeLists.txt` at line 62, Update the version declaration in build.zig.zon
from 0.2.0 to 0.2.1 so it matches the project version in CMakeLists.txt,
pkg-config metadata, and idf_component.yml.
Version bump for v0.2.1. Ten commits have landed since v0.2.0, four of them touching shipped sources, and two of those are fail-closed fixes that consumers on the current release do not have.
Why now
src/nip17.cpreviously continued sealing and wrapping when the RNG draw for timestamp fuzzing failed, producing an event with an unfuzzed timestamp rather than an error. Both call sites now destroy the partial event, clear the out-parameter, free the intermediate ciphertexts and wipe the ephemeral private key.src/key.cnow lets the ESP32 RNG report failure the way every other backend does, so a degraded draw surfaces instead of being silently accepted.Anyone consuming this library by release is on v0.2.0 without either. Consumers pinning by commit already have them.
Changes
CMakeLists.txt: project version to 0.2.1idf_component.yml: component version to 0.2.1, so the ESP-IDF component registry matchesCHANGELOG.md: 0.2.1 entry covering the security fixes, the FreeRTOS task-create fix, the macOS OpenSSL and Windows CI fixes, and the QEMU smoke testSOVERSIONstays at 1: no ABI change.Verification
Configured and built from clean, producing
libnostr.so.0.2.1, which confirms the bump reaches the built artifact rather than only the manifests. Full suite run: 15 of 15 passed.Summary by CodeRabbit
Documentation
Release