ci: use shared Ruby release validator - #706
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
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.
Replace the repository-local release validator and its tests with
appium/appium-workflows/.github/actions/ruby-release-validate, pinned to the merged commit from appium/appium-workflows#12.Both PR package validation and tagged publication use the shared action. Artifact upload consumes its absolute
gem-path; the separate publication job receives only the filename and publishes the downloaded artifact from its ownpkg/directory. The existing publication workflow, environment, and RubyGems Trusted Publisher configuration are unchanged.Remove duplicated helper/tests and update the runbook for local verification and date recovery through the shared repository. Application tests remain in place.
Validation: local gem build, shared action validation against the built gem, simulated cross-job artifact path transfer, actionlint, and whitespace checks passed. No publication was performed. The shared action has passing Ruby 3.1/3.4/4.0 tests in its own repository.