Bump [package].version to 0.1.9 for the solmem-chain release

[thedavidmeister]

#560 shipped the solmem 0.1.26 dep chain without bumping [package].version, and the Package Release gate refuses to publish a version that is not ahead of the published revision (its exact error on the July run: "foundry.toml [package].version (0.1.8) is not ahead of the published revision (0.1.8)").

Patch is honest for this release: the interface migration swaps which package provides the same types (rainlang-interface 0.2.5's source delta vs the orphaned rain-interpreter-interface is import pins only), and the solmem/datacontract/extrospection/math-binary bumps move internals and generated pointers, not rainlang's own API.

Note: publish is ALSO blocked by a dead credential — the repo-level PUBLISH_PRIVATE_KEY (set 2026-05-26) shadows the working org-level secret and its counterpart key no longer exists anywhere (today's run 32590826123 dies at checkout with "Permission denied (publickey)"). The repo secret needs deleting so the org secret flows through, as it does on every repo that published today.

QA

• Discriminating tests: n/a — one-line version metadata edit in foundry.toml; no executable code in the diff, so no test can distinguish it. The release gate itself discriminates: it hard-fails any version not strictly ahead of the published 0.1.8.
• Mutations applied: n/a — no logic to mutate; the only possible mutation (a different version string) is exactly what the release gate adjudicates.
• Oracle: the soldeer registry's published revision list (rainlang 0.1.8 latest, 2026-07-03) and the Package Release gate's own error text demanding the next unpublished version.
• Category check: unblocks the Bump rain-solmem 0.1.3 -> 0.1.26 (and the dep chain pinning it) #560 release chain; covers exactly the version-bump requirement, nothing else.

Summary by CodeRabbit

• Chores
  • Updated the package version to 0.1.9.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 39a53280-aa07-45ec-a795-60d26abf8fec

📥 Commits

Reviewing files that changed from the base of the PR and between 1fad1fd and 8fb0d2e.

📒 Files selected for processing (1)

• foundry.toml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The package version in foundry.toml was incremented from 0.1.8 to 0.1.9.

Changes

Package version

Layer / File(s)	Summary
Update package version foundry.toml	The package version changed from 0.1.8 to 0.1.9.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 8fb0d

This localized metadata-only change advances the package version to unblock the release gate; no actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: dcatki

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the version change in foundry.toml and its purpose for the solmem-chain release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump-version-0.1.9

---

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.}

[thedavidmeister]

Holding this: under the tag-release lifecycle that the standards migration moves rainlang onto, [external.package].version records the LAST publish, not the next one — so 0.1.8 is correct on main and this bump to 0.1.9 would break the release guard's version==tag check rather than unblock it.

The publish failure this PR was written to fix has a different cause: the repo-level PUBLISH_PRIVATE_KEY secret (set 2026-05-26) shadows the working org secret and its key no longer exists, so checkout dies with Permission denied (publickey). That secret still needs deleting for the crates half; tag-release is push-free and does not need it for the soldeer half.

A 0.1.9 release under the new lifecycle is: deploy → a PR that runs cutRelease() (freezing src/generated/0_1_9/) and bumps the version in lockstep → merge → push sol-v0.1.9. Superseded by the migration PR unless the migration is abandoned.

[thedavidmeister]

Closing: superseded by #563, which moved this repo to the tag-driven release lifecycle. Under tag-release, [external.package].version records the LAST publish, so 0.1.8 on main is correct and this bump to 0.1.9 would fail release-guard's version==tag check rather than unblock anything.

A 0.1.9 release is now: deploy to the networks that lack the suites → a PR running cutRelease() (freezing src/generated/0_1_9/) and bumping the version in lockstep → merge → push sol-v0.1.9.

The publish failure this PR was written to fix also had a different cause, and it is not fully fixed by deleting the dead repo secret — see rainix#358: the crates lane pushes to a protected main, so removing the key moves the failure from checkout to GH006 on push. The soldeer half is unwedged by #563 because tag-release commits nothing.