Repository navigation
chore: prepare version 1.0.4 - #97
Merged
Merged
Conversation
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.
|
Docs7 for cardmagic/solid-objects-ruby
Commit |
[Low impact] The changes stay within project documentation and release labels. The PR appears safe to merge, with one non-blocking changelog correction. Findings
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.SummaryPrepares version 1.0.4 with shorter README maturity notes.
Reviews (1) · Last reviewed commit: "chore: prepare version 1.0.4" · Reviewed by Greptile |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/versioning.mdkeeps 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.Checks