Skip to content

Releases: robotmoney/robotmoney-core

v0.3.3

Choose a tag to compare

@github-actions github-actions released this 23 Jul 20:44
1d83fc2
feat(adapters): Uniswap V3 AssetPositionAdapter (custody + swap + TWA…

v0.3.2

Choose a tag to compare

@github-actions github-actions released this 10 Jul 16:03
0956f09
Add rmpc support for MCP committee identity and payload signing (#1112)

* chore: initialize issue #1111 worktree

* feat(rmpc): add committee-identity — MCP committee Ed25519 signing identity

Adds `rmpc committee-identity create|show-public-key|sign`: a local,
encrypted-at-rest Ed25519 identity distinct from the on-chain EVM signer
used by `rmpc committee register`/`vote-submit`. Matches the
robotmoney-frontend Investment Committee demo's existing wire format
exactly (raw 32-byte Ed25519 public key / raw 64-byte signature, standard
base64) so a prospective agent can apply, sign the canonical
get_signing_payload string, and submit_recommendation without hand-rolling
crypto — and with zero changes needed on the frontend side.

Closes #1111

* chore(docs): regenerate stale contract NatSpec docs (org URL drift)

contracts/doc/src/contracts/ and book.toml still referenced the retired
robotmoney-monorepo org/repo name in every [Git Source] link, failing the
generated-docs-freshness CI gate (pre-existing drift on dev, unrelated to
this PR's rmpc changes — same class as the org-rename drift fixed once
before in #870). Regenerated via `forge doc`; every changed line is the
git-repository-url/Git-Source URL, no NatSpec content changed.

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 23 Jun 13:30
35f28b3
docs: retire stale scan_residual_seams.rs scout modules — residual bu…

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 19 Jun 04:13
56b499a
phase(contract-security-remediation): land completed Contract securit…

v0.2.2

Choose a tag to compare

@github-actions github-actions released this 05 Jun 15:19
e43693b
feat(dapp): show Drip button on onboarding step 1 when wallet has zer…

v0.0.1

Choose a tag to compare

@github-actions github-actions released this 12 May 01:11
refactor(release-rmpc): build first, tag+publish only on success

Old order created+pushed the tag before any build ran, so a build failure
left an orphan tag pointing at a commit whose binaries couldn't be
produced. New order:

  resolve -> build (matrix x4, uploads artifacts) -> publish

Publish job runs only after every build succeeds. It downloads all four
archives, creates+pushes the tag, and creates the GitHub Release with
all assets in one step. dry_run mode skips publish entirely.

Other changes:
- New resolve job expands short-form commit_hash via git rev-parse and
  emits a single canonical SHA + version string consumed by both build
  and publish, so checkout no longer fails when given a 7-char SHA.
- commit_hash defaults to github.sha so dispatching --ref <branch>
  builds that branch's HEAD with no extra input.
- Tag input is validated up front in resolve, not deep in the matrix.