Skip to content

chore: release 0.14.5 with the Ruby state warning parity row - #34

Merged
cardmagic merged 2 commits into
mainfrom
docs/record-ruby-state-warning-parity
Aug 29, 2026
Merged

chore: release 0.14.5 with the Ruby state warning parity row#34
cardmagic merged 2 commits into
mainfrom
docs/record-ruby-state-warning-parity

Conversation

@cardmagic

@cardmagic cardmagic commented Aug 29, 2026

Copy link
Copy Markdown
Owner

The port this repo already shipped in 0.14.4 now exists on the Ruby side, so
the parity ledger row is stale. It says the Ruby gem "has no soft threshold
yet" and points at cardmagic/solid-objects-ruby#57, which is fixed by
cardmagic/solid-objects-ruby#58.

What changed

docs/parity.md, one row. "Large committed state warning" now records that the
Ruby gem carries the same solid_objects.state.large event and the same 5 MB
hard default from 0.14.3, under warn_state_bytes, and that its threshold
defaults to 64 KB rather than 128 KB.

The defaults differ on purpose. Each is taken from its own measured curve: the
gem keeps 55% of its empty-state throughput at 13 KB of state, where this
package keeps 98% at 16 KB. Sharing one number would either warn a Node
application too early or warn a Rails application too late.

Version 0.14.5, a patch. The ledger correction carries no runtime change, so
package.json, src/version.ts, and CHANGELOG.md move together the way
0.14.4 did.

No source change beyond the version constant. Nothing else in the ledger was
stale: the Ruby gem also cut its per-turn state copies and stopped encoding a
discarded string, but those are internal costs rather than ledger capabilities.
The remaining table lines in the diff are Prettier re-padding the column to the
new width.

Merge order

Merge after cardmagic/solid-objects-ruby#58, which is what makes the Ruby claim
in this row true.

Validation

pnpm run format:check   # All matched files use Prettier code style
pnpm run check          # parameters, documentation, browser imports, tsc
pnpm test               # 50 files, 356 passed, 13 skipped

The row said the Ruby gem has no soft threshold. It carries the same
solid_objects.state.large event from 0.14.3, as warn_state_bytes, and
the same 5 MB hard default.

Its threshold defaults to 64 KB rather than 128 KB, because the measured
Ruby curve falls sooner: the gem keeps 55% of its empty-state throughput
at 13 KB of state, where this package keeps 98% at 16 KB.
@greptile-apps

greptile-apps Bot commented Aug 29, 2026

Copy link
Copy Markdown

Greptile Summary

Updates the parity ledger to record the Ruby implementation of large committed-state warnings and explain why its warning threshold differs from the JavaScript package.

  • Documents the shared instrumentation event and 5 MB hard limit.
  • Records the Ruby 64 KB soft threshold alongside the JavaScript 128 KB threshold.
  • Adds benchmark context for the intentionally different defaults.

Confidence Score: 5/5

The documentation-only change appears safe to merge after the stated Ruby dependency is merged.

The JavaScript event name, post-commit timing, limits, and benchmark statement are supported by repository code and documentation, and no changed-code defect or rule violation remains.

Important Files Changed

Filename Overview
docs/parity.md The updated JavaScript claims agree with local implementation, tests, and benchmark documentation; no actionable defect was identified.

Reviews (1): Last reviewed commit: "docs: record the Ruby state warning in t..." | Re-trigger Greptile

A parity ledger correction with no runtime change, so this is a patch.
@cardmagic cardmagic changed the title docs: record the Ruby state warning in the ledger chore: release 0.14.5 with the Ruby state warning parity row Aug 29, 2026
@cardmagic
cardmagic merged commit edced2c into main Aug 29, 2026
18 checks passed
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