Repository navigation
Conversation
lutzcc1
previously approved these changes
Sep 9, 2026
nz
marked this pull request as draft
September 9, 2026 01:41
The changelog stopped at 0.4.1 while ten more versions shipped to rubygems. Reconstruct each from the version.rb bumps, the merged pull requests between them, and the diffs, so a consumer can tell what a version changed for them. 0.8.1 published from an uncommitted bump, so its contents are read back out of the built gem, which matches the tree at the merge of pull request #46. Correct two entries while here: 0.4.1 was dated a year early, which put it out of order, and 0.3.0 was written as a second 0.2.0.
The ActiveRecord integration reaches every boundary a converted model crosses: readers, writers, query binds, validation and serialization. Name the release for that, and date the section the day it ships.
The 0.9.0 section now carries every bullet that accumulated under Unreleased, grouped by the area it touches rather than by the pull request it arrived in, and an Upgrading from 0.8.x subsection names the four changes an application has to sweep for: a reader override that composes through super, encrypted attributes reading as Options, the core and ActiveRecord seams that no longer unwrap, and delegate_optional calling its target directly. Also drops the three em-dashes from the README and the changelog.
lutzcc1
previously approved these changes
Sep 9, 2026
lutzcc1
approved these changes
Sep 9, 2026
nz
disabled auto-merge
September 9, 2026 15:01
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.
Merge last, after #69, #70, and #71. Their Unreleased bullets move under 0.9.0 on the rebase that follows; the placeholder comment at the end of the section marks the spot.
Two commits. The first backfills
CHANGELOG.mdfrom 0.4.0 through 0.8.3, which the file had never recorded, reconstructed from theversion.rbbump commits, the merged PRs between them, and the diffs, with published versions and dates confirmed against rubygems since the repository has no tags. It also fixes two errors in the existing entries: the second[0.2.0]heading was 0.3.0, and 0.4.1 was dated a year early, which is what put the file out of order.The second bumps the version to 0.9.0 (
Gemfile.lockfollows throughbundle lock --add-checksums, two lines) and dates the section 2026-09-08 with a lead sentence: the release turns the ActiveRecord integration from wrapping readers into a full set of boundaries, and it carries behavior changes.Findings from the reconstruction, for the record:
Verified locally: rubocop (no new offenses), rake test, yard doctest,
nix build .#errgonomicproducingerrgonomic-0.9.0.