Development -> master : with fully functional CI into master for auto triggering#407
Merged
Conversation
…helpers Extract package build/import and Maven wrapper publish/validate into scripts so RC workflows stay thin and repeatable. Co-authored-by: Cursor <cursoragent@cursor.com>
Update machine-readable release and test plans for the new RC pipeline stages. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…sed E2E Build .unitypackage artifacts before E2E, pass them via workflow artifacts, and import into test-app instead of testing from raw Assets. Co-authored-by: Cursor <cursoragent@cursor.com>
Run smoke scenarios against the GitHub prerelease artifact and post rc-smoke/github-release check-run for promotion gating. Co-authored-by: Cursor <cursoragent@cursor.com>
… path Require rc-smoke success before RC-PROMOTE and restrict production workflow to releases/* branches merged to master. Co-authored-by: Cursor <cursoragent@cursor.com>
Replace broken platform-only workflows with a single manual entrypoint. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Replace curl-based CI_SLACK_TOKEN notifications with shared scripts for Capacitor-style webhook payloads. Remove release_QA push workflow and checkJira.sh; production release workflow keeps only GitHub release creation. Co-authored-by: Cursor <cursoragent@cursor.com>
Post RC, smoke failure, promote failure, and production notifications via slackapi/slack-github-action and CI_SLACK_WEBHOOK_URL. Use CI_JIRA_EMAIL/TOKEN for fixVersion tickets. Skip Slack on dry_run RCs; apply PR #201 changelog safe-extract and continue-on-error on send steps. Co-authored-by: Cursor <cursoragent@cursor.com>
Jira tickets use fix versions like Unity SDK v6.18.0; guard the fetch script against accidental -rcN values in callers. Co-authored-by: Cursor <cursoragent@cursor.com>
Parse Unity CHANGELOG "## vX.Y.Z" sections and "*" bullets. Include changes in RC success Slack alongside Jira tickets; production path benefits too. Co-authored-by: Cursor <cursoragent@cursor.com>
- Add reusable playmode workflow to rc-release; run parallel with E2E and block rc-publish - Materialize .unitypackage assets from RC prerelease for production checks and GitHub release upload - Remove legacy activation and main workflows; update rc-plan, Slack legs, and CI badges
- Sync iOS Purchase Connector with iOS SDK in bump-version, README, and Introduction - Add RC verify checks for PurchaseConnector pod and README version lines - Extend production Slack to report Purchase Connector versions and block README drift - Wrap RC and production success Slack messages with unity emoji borders
Complete Unity RC/production CI/CD pipeline aligned with mobile plugin tooling
- Allow playmode unit tests to publish GitHub Checks from RC release - Grant GHCR package read access for Android E2E in RC release and smoke - Align manual Android E2E job permissions with the reusable workflow
- Bump VERSION_CODE in gradle.properties when the unity-wrapper version changes - Append SDK and plugin version bullets to existing ## vX.Y.Z sections instead of RC headers - Skip duplicate VERSION_CODE increment when Maven publish runs after bump-version.sh - Verify VERSION_CODE increases against the base branch in the RC release workflow
- Serialize Android E2E after iOS in RC and manual runs - Allow Android Unity builds after package import mutates test-app - Use simulator launch deep-link triggers for iOS E2E and smoke plans
- Use API 33 Google APIs emulator with Pixel 6 resources and DNS checks - Add HOME settling before Android deep-link triggers in E2E and smoke plans - Preserve pre-action execution and guard Android onNewIntent forwarding (testapp only)
- Build production artifacts from promoted master metadata - Validate package contents reject RC version metadata - Consume production artifacts for package checks and release upload - Preserve existing UPM branch and tag behavior
Kobikg78
approved these changes
May 31, 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.
No description provided.