Repository navigation
docs(changelog): add the v0.7.0 upgrade notes - #127
Merged
Merged
Conversation
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.
Why
v0.7.0 shipped the breaking
StoredRowchange from #126. Module authors upgrading from 0.6 need to know what to change. Per AGENTS.md, the release commit writesCHANGELOG.mdand the upgrade notes for that version follow in their owndocs(changelog)PR.What
CHANGELOG.mdgains a### Upgrade notessection under v0.7.0, in the place v0.4.0's sits. It covers:RowFieldsand the public signatures that now takeStoredRow;500refusals of a getter result, a decorated field default, a setter write and a related row;thisinside a getter or setter.The text is the one listed in #126's body, with a link to #126 on each item.
Proof
Documentation only.