Skip to content

chore: upgrade rustledger to v0.24.0 - #321

Closed
rustledger-bot[bot] wants to merge 1 commit into
mainfrom
chore/upgrade-rustledger-v0.24.0
Closed

rustledger-bot[bot] wants to merge 1 commit into
mainfrom
chore/upgrade-rustledger-v0.24.0

Conversation

@rustledger-bot

@rustledger-bot rustledger-bot Bot commented Sep 6, 2026

Copy link
Copy Markdown

Automated update of rustledger WASM version to v0.24.0.

The component's WIT version matches the host bindings (3.11.0) and the release notes carry no breaking markers, so this auto-merges once CI passes. The component was sha256-verified against the release asset.

See rustledger releases for the changelog.

@rustledger-bot
rustledger-bot Bot enabled auto-merge (squash) September 6, 2026 22:17
robcohen added a commit that referenced this pull request Sep 16, 2026
The snapshot refresh in the previous commit is only correct against
rustledger v0.24.0 or newer, so the pin has to move with it. The two are
one change: separately, each is red.

#321 (the bot's v0.24.0 bump) has been stuck since 2026-09-06 failing on
exactly the four tests the previous commit fixes, and while it stays
stuck the pin sits at v0.22.0 -- which is in turn why rustledger's
`Downstream (rustfava)` check, which tests against rustledger main, has
been red since 2026-09-01 (rustledger#2302). This supersedes #321.

Verified against the RELEASED v0.24.0 component, resolved the way CI
resolves it rather than through the RUSTLEDGER_COMPONENT_WASM override:
679 passed, 1 skipped, 100% coverage. The same snapshots also pass
against a component built from rustledger main (6972f5edd1).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012nNGPA44Dt32NyxWem26xr
robcohen added a commit that referenced this pull request Sep 16, 2026
`RUSTLEDGER_VERSION` moves v0.22.0 -> v0.24.0, and the four snapshots move with
it. Separately each is red: the bumped pin produces output the old snapshots
reject (#321, stuck since 2026-09-06), and refreshed snapshots do not match what
v0.22.0's component emits.

That deadlock is the whole of rustledger#2302. The snapshots went stale, so the
upgrade bot's PR could not go green, so the pin stayed two releases behind, so
rustledger's `Downstream (rustfava)` check -- which tests against rustledger
main -- stayed red on the same four tests since 2026-09-01. A check that is
always red gives no signal, which is the thing being fixed here.

Both snapshot causes were confirmed against the oracle, not assumed:

- `document` directives carry tags and links. beancount 3.2.3 reads
  `2012-12-15 document Expenses:Food "./import.csv" #tag ^link1` as
  `tags=['tag'] links=['link1']`. Compare beancount#2160, where `Note` gained the same
  two fields.
- an unaliased function column is named with the whole expression, `sum(day)`
  and `units(position)`. beanquery 0.2.0 names them the same way.

Six changed values across four snapshot files, each attributable to one of
those. Verified against the released v0.24.0 component the way CI resolves it,
and against a component built from rustledger main: 679 passed, 1 skipped,
100% coverage on both.

Closes rustledger/rustledger#2302
Supersedes #321

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012nNGPA44Dt32NyxWem26xr
@robcohen

Copy link
Copy Markdown
Member

Superseded by #325, which carries this same v0.22.0 -> v0.24.0 bump together with the four snapshot updates it requires. Separately each was red, which is why this sat since 2026-09-06; together they are green.

@robcohen robcohen closed this Sep 16, 2026
auto-merge was automatically disabled September 16, 2026 18:49

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant