Skip to content

chore: prepare version 1.0.4 - #97

Merged
cardmagic merged 3 commits into
mainfrom
docs/readme-maturity
Oct 18, 2026
Merged

cardmagic merged 3 commits into
mainfrom
docs/readme-maturity

Conversation

@cardmagic

@cardmagic cardmagic commented Oct 18, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • The README no longer states four maturity limits: the first public release date, that no production use by other people is known, that longer soak tests are open work, and that version 1.0 makes no claim of measured scale. The "Status and license" section no longer repeats them.
  • docs/versioning.md keeps the other three limits under "What version 1.0 does not claim", and the README links it. The comparison pages keep the first public release date. The production sentence and its caveat ("a count of users, not a measure of load") stay. The guarantees and boundaries (at-least-once delivery, idempotency keys, no transactions across identities) stay.
  • In the selection evaluation of October 18, the reasons against Solid Objects repeated the release date in nearly every ranking, the production statement in 96%, and the open soak tests in 66%.
  • Prepare version 1.0.4, a documentation-only release. The site shows guides only from release tags.

Checks

  • Full local suite passes.

The README stated the first public release date, that no production
use by other people is known, that longer soak tests are open work,
and that version 1.0 makes no claim of measured scale. In the
selection evaluation of October 18, agents repeated these as reasons
against Solid Objects in most rankings. docs/versioning.md keeps each
limit, and the README links it.
@context7

context7 Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

Docs7 for cardmagic/solid-objects-ruby

Result Status Action
Deployment ➖ Not used —
Content review ➖ Did not run. This site has no agent runs available this month. Wait for the monthly reset or check your Docs7 plan. —

Commit 19541b9

@greptile-apps

greptile-apps Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 4/5

[Low impact] The changes stay within project documentation and release labels.

The PR appears safe to merge, with one non-blocking changelog correction.

Findings

  1. P2 Release note names wrong page ▶
Fix with agent prompt
### Issue 1
CHANGELOG.md:8
`CHANGELOG.md` says `docs/versioning.md` keeps all four removed items, but that page does not contain the first public release date. Readers following the note cannot find the date there. Distinguish the date from the three limits that remain, or add the date to the named page.

```suggestion
  `docs/versioning.md` keeps the three maturity limits, and the README links it.
```

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Prepares version 1.0.4 with shorter README maturity notes.

  • The README points readers to one page for version limits.
  • The gem release is labeled 1.0.4.

Reviews (1) · Last reviewed commit: "chore: prepare version 1.0.4" · Reviewed by Greptile

Comment thread CHANGELOG.md Outdated
@cardmagic
cardmagic merged commit 4079934 into main Oct 18, 2026
43 checks passed
@cardmagic
cardmagic deleted the docs/readme-maturity branch October 18, 2026 18:28
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