chore: prepare v2.0.0.beta4 - #286
Merged
Merged
Conversation
beta3 fixed the canonical entry points and shipped almost none of the behaviour. beta4 is the prerelease the 2.0.0 entry actually describes: the four green-suite bugs (#254 #255 #256 #258), the accept workflow (#259), the legible failure message (#264), and the deprecation warnings that make 2.1's removals visible (#246 #263). - `lib/snap_diff/version.rb` -> 2.0.0.beta4. Nothing else holds a version; the gemspec, the legacy version file and the mirror gemspec all read it. Verified with the release workflow's own guard command: `ruby -I lib -r capybara/screenshot/diff/version -e "puts Capybara::Screenshot::Diff::VERSION"` => 2.0.0.beta4 - CHANGELOG: a `[v2.0.0.beta4]` section written as the delta from beta3, plus the record-modes PLACEHOLDER filled from #259 now that it has shipped. `grep -n PLACEHOLDER CHANGELOG.md` returns nothing. - Install snippets moved beta3 -> beta4 in README, docs/UPGRADING.md and docs/migration-guide.md. They stay PINNED: `~> 2.0` resolves to nothing while only prereleases exist, so unpinning belongs to 2.0.0 final, not here. The notes name the #272 caveat explicitly. Removing `skip_area`'s implicit stabilization wait (10.012 s -> 0.009 s measured) means a selector not yet in the DOM now yields no mask, silently, where it previously resolved after the wait. #277's run-level tally shipped in the same beta as the replacement signal, and the notes say so rather than leaving it to be discovered. Gates: `rake test:unit` 720 runs / 2124 assertions / 0 failures / 0 skips under CI=true on 4.0.6, `standardrb lib test` clean over 161 files, and `gem build` produces capybara-screenshot-diff-2.0.0.beta4.gem (93 files, 13 docs, RELEASE_PREP correctly excluded).
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Contributor
Reviewer's GuidePrepares the 2.0.0.beta4 prerelease without production code changes by bumping the sole version constant, documenting the shipped behavior and known skip_area caveat, completing record-mode release notes, and updating all current prerelease installation pins and release guidance. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe project version changed to ChangesBeta4 release update
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This PR updates the prerelease version and aligns release documentation and installation guidance; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
1 participant
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.
Prepares the
2.0.0.beta4prerelease. Docs, CHANGELOG and version only — no code changes.beta3 fixed the canonical entry points and shipped almost none of the behaviour. beta4 is the
prerelease the
[v2.0.0]CHANGELOG entry actually describes: the four green-suite bugs(#254 #255 #256 #258), the accept workflow (#259), the legible failure message (#264), and the
deprecation warnings that make 2.1's removals visible (#246 #263).
If you are on beta3, this is not an optional bump — beta3 still passes green on a screenshot
it never compared.
What's in the diff
lib/snap_diff/version.rb→2.0.0.beta4. Nothing else holds a version.[v2.0.0.beta4]CHANGELOG section, written as the delta from beta3, with the skip_area selectors that match nothing block for 5s each — measured at 44% of a real suite #272 caveatnamed explicitly rather than left to be discovered.
PLACEHOLDERfilled from Accept-workflow and honest reporting: adopt what Playwright, VCR and SimpleCov already proved #259 now that it has shipped.grep -n PLACEHOLDER CHANGELOG.mdreturns nothing.docs/UPGRADING.md,docs/migration-guide.md.They stay pinned:
~> 2.0resolves to nothing while only prereleases exist, so unpinningbelongs to 2.0.0 final or
bundle installhard-fails.Verification
The release workflow's version guard reads a different constant than the one bumped
(
Capybara::Screenshot::Diff::VERSION, via the legacy shim), so it was run exactly asrelease.ymldoes rather than assumed:rake test(both suites)standardrbgem buildcapybara-screenshot-diff-2.0.0.beta4.gem— 93 files, 13 docs,RELEASE_PREPexcludedgrep PLACEHOLDERbeta3pinsThe single skip is pre-existing: CI's own pre-#283 run reported
757 runs … 1 skipstoo. Whatchanged there is
6 errors → 0 errors.The caveat, stated in the release notes
Removing
skip_area's implicit stabilization wait (#272, measured 10.012 s → 0.009 s) means aselector not yet in the DOM now yields no mask, silently, where it previously resolved after
the wait. #277's run-level tally shipped in the same beta as the replacement signal — the notes
say so rather than leaving a user to find out from a flaky mask.
After merge
Dispatch Actions → Release with input
2.0.0.beta4, then verify both gem names published atthe same version (a version under only one name is the failure mode to watch — the dual-install
guard assumes they never diverge), then re-verify against a real consumer.
Summary by Sourcery
Prepare the 2.0.0.beta4 prerelease by updating the version and aligning release documentation and installation pins.
Enhancements:
Documentation:
Chores:
Summary by CodeRabbit
Release
Documentation