release v1.0.2-beta.0#39
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
# Conflicts: # percy/version.rb
pranavz28
approved these changes
Jun 29, 2026
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
2 participants
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.
Bumps the SDK to the next beta (
1.0.1→1.0.2-beta.0) for a beta release.Note on the corrected target version: this PR originally targeted
0.0.10-beta.0, but that target became stale. After this PR was opened,mainreleased0.0.9(#36) and then1.0.1(#38), somain'spercy/version.rbis nowVERSION = '1.0.1'.0.0.10-beta.0is lower than1.0.1, which both made the branch conflict and made it an invalid (lower) release target. The branch has now been merged withmainand the version corrected to the next patch-base beta after1.0.1:1.0.2-beta.0(hyphenated-beta.0per repo convention).The branch name stays
release/v0.0.10-beta.0— it is cosmetic, and renaming an open PR's branch is disruptive (it would break the existing PR ref and any local checkouts). Only the released version string (percy/version.rb) matters for the gem, and that is correct at1.0.2-beta.0.🤖 Generated with Claude Code