Release v1.0.1#38
Merged
Merged
Conversation
Bump version to 1.0.1. Supersedes the stray 1.0.0 (published 2024-10-28) that RubyGems resolves as `latest` due to semver ordering but which is broken with real Appium drivers (strict platformName lookup -> PlatformNotSupported -> empty build). 1.0.1 is cut from current main, so `gem install percy-appium-app` now resolves to working code that also includes appium_lib_core 13.x support (PR #37). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
|
||
| module Percy | ||
| VERSION = '0.0.9'.freeze | ||
| VERSION = '1.0.1'.freeze |
Contributor
Author
There was a problem hiding this comment.
1.0.0 actually is already released initially
Shivanshu-07
approved these changes
Jun 25, 2026
Merged
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.
What
Bump version
0.0.9→1.0.1.Why
RubyGems resolves the
latestofpercy-appium-appby semver ordering, so it currently points at a stray1.0.0published 2024-10-28 — which sorts above our real release line (0.0.9). That1.0.0is broken with real Appium drivers: itsMetadataResolverdoes a strictcapabilities.fetch('platformName'), butdriver.capabilities.as_jsonyields snake_case keys, so it raisesPlatformNotSupportedand silently takes no snapshot (build finalizes empty).Net effect today:
gem install percy-appium-app(no version pin) installs the broken1.0.0.Cutting
1.0.1from currentmainmakeslatestresolve to working code again (1.0.1 > 1.0.0 > 0.0.9), without needing to yank1.0.0.What's included
1.0.1is cut frommainafter merging the appium_lib_core 13.x fix (#37), so this release:PlatformNotSupported/ empty-build failure on the latestappium_lib.Verification
The code is identical to the merged #37 state, which was verified by:
🤖 Generated with Claude Code