fix: revert v0.2.2 and add fix for dependency

[sporicle]

Summary by CodeRabbit

• Chores
  • Released version updates across package templates and workspace to 0.2.3.
  • Updated workspace dependencies to align package versions.
  • Refined Solana program compatibility constraints for broader compatibility.
  • Simplified internal program ID handling and related code paths — no user-facing API changes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Bumps package and crate versions and tightens a Solana constraint; refactors SDK PDA helpers to use Pubkey and crate::id() instead of a SolanaPubkey alias and consts::VRF_PROGRAM_ID.

Changes

Cohort / File(s)	Summary
NPM package template \.github/packages/npm-package/package.json.tmpl	Updated version from 0.2.2 → 0.2.3.
Cargo workspace & manifests Cargo.toml	Workspace package version bumped 0.2.2 → 0.2.3; ephemeral-vrf, ephemeral-vrf-api, ephemeral-vrf-sdk-vrf-macro dependencies updated to 0.2.3; solana-program constraint changed to >=1.18.26, <3.
SDK PDA refactoring sdk/src/pda.rs	Replaced SolanaPubkey alias with direct Pubkey use; switched calls to Pubkey::find_program_address; replaced consts::VRF_PROGRAM_ID with crate::id(); removed alias import. Public function signatures/returns unchanged.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Release/v0.2.2 #41: Modifies the same sdk/src/pda.rs PDA derivation helpers and addresses SolanaPubkey / program ID usage overlap.
• fix: support for anchor 0.32.1 #31: Changes crate::id() and Pubkey usage patterns that intersect with the PDA refactor in this PR.

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title mentions reverting v0.2.2 and adding a dependency fix, but the actual changes show a version bump from 0.2.2 to 0.2.3, dependency updates, and code refactoring in pda.rs — not a revert.	Update the title to accurately reflect the main changes, such as 'chore: bump version to 0.2.3 and update solana-program constraint' or 'refactor: update PDA derivation to use Pubkey::find_program_address'.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/v0.2.3

---

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: 2

🤖 Fix all issues with AI agents

In @.github/packages/npm-package/package.json.tmpl:
- Line 4: The package.json.tmpl "version" field is out of sync with the release
tag; update the "version" property value in
.github/packages/npm-package/package.json.tmpl from "0.2.1" to the intended
release version (e.g., "0.2.3") so the npm package metadata matches the
release/workspace version, or confirm the correct target version and set the
"version" key accordingly.

In `@Cargo.toml`:
- Line 6: The workspace Cargo.toml version value ("version = \"0.2.1\"") and any
internal crate version entries must be updated to match the intended release tag
(release/v0.2.3); locate the top-level "version" field and the per-crate version
fields referenced later (the entries around the other version occurrences
mentioned) and change them to "0.2.3" so workspace and internal crate versions
are consistent with the release branch.