feat: automated RC release pipeline with .unitypackage build and E2E tests#405
Open
Kobikg78 wants to merge 8 commits into
Open
feat: automated RC release pipeline with .unitypackage build and E2E tests#405Kobikg78 wants to merge 8 commits into
Kobikg78 wants to merge 8 commits into
Conversation
After both E2E jobs pass, build regular and strict .unitypackage artifacts using Unity 6000 on macOS and commit them to the release branch — replacing the manual local build step. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Build .unitypackage first, then run iOS E2E, then Android E2E. Matches the manual process: artifact built before testing. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Both iOS and Android E2E workflows now: 1. Delete test-app/Assets/AppsFlyer 2. Import the built .unitypackage before building the test app This tests the actual artifact that will be shipped to customers. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Both iOS and Android E2E workflows now import the built .unitypackage into the repo root project (not test-app), matching the UPM local reference in test-app/Packages/manifest.json (file:../../Assets/AppsFlyer). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…d E2E Avoids Unity license activation inside Docker for the import step. A .unitypackage is a tar.gz archive — extract directly on the runner using pathname metadata to restore files to their correct paths. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Tar extraction of .unitypackage omits Tests/ and Mac/ folders that exist in the release branch, leaving git in a dirty state. Setting allowDirtyBuild: true lets game-ci proceed regardless. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
game-ci runs Docker internally and doesn't inherit the runner's login session. Pass registryUrl/Username/Password so it can pull from GHCR. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
build-packagejob to RC pipeline that builds both regular and strict.unitypackageartifacts before E2E runs.unitypackageinto the repo root (matching UPM local reference intest-app/Packages/manifest.json)Test plan
plugins-effort-reduction-workflow1🤖 Generated with Claude Code