feat: runway

[itsyoboieltr]

Description

This PR adds the Runway GitHub Action to help upload our builds and releases to Runway for easier release management. As Runway has a GitHub App connected to our repository, it is enough to upload builds as GitHub artifacts, and they will be automatically pulled. Currently the builds are downloaded from CircleCI, so later, once builds are migrated to GitHub Actions, this workflow will need to be updated.

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/3619

Manual testing steps

1. Builds should show up in Runway.

Screenshots/Recordings

Not applicable

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[metamaskbot]

Builds ready [2ffb616]

• builds: chrome, firefox
• builds (flask): chrome, firefox
• builds (MMI): chrome
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6, 7
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
  • ui: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
  • content-script: 0
  • offscreen: 0

Page Load Metrics (1645 ± 59 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1475	1879	1648	119	57
		domContentLoaded	1464	1858	1618	121	58
		load	1473	1884	1645	123	59
		domInteractive	23	187	47	40	19
		backgroundConnect	9	77	31	19	9
		firstReactRender	15	95	40	26	13
		getState	4	55	14	15	7
		initialActions	0	1	0	0	0
		loadScripts	1066	1418	1216	110	53
		setupStore	6	87	18	25	12
		uiStartup	1646	2534	1940	224	108

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 203 Bytes (0.00%)
• common: 0 Bytes (0.00%)

[metamaskbot]

Builds ready [b462c5c]

• builds: chrome, firefox
• builds (flask): chrome, firefox
• builds (MMI): chrome
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6, 7
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
  • ui: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
  • content-script: 0
  • offscreen: 0

Page Load Metrics (1805 ± 73 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1580	2299	1813	169	81
		domContentLoaded	1553	2096	1778	149	71
		load	1563	2123	1805	153	73
		domInteractive	24	88	45	19	9
		backgroundConnect	8	59	24	16	8
		firstReactRender	17	102	48	32	15
		getState	5	68	16	17	8
		initialActions	0	1	0	0	0
		loadScripts	1099	1624	1336	147	71
		setupStore	6	78	28	27	13
		uiStartup	1736	2639	2180	256	123

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 43 Bytes (0.00%)
• ui: 203 Bytes (0.00%)
• common: 0 Bytes (0.00%)

[Gudahtt]

There is something odd about the .zip file artifacts. When testing, they work if I load the unzipped directories as an unpacked extension (in Chrome). But if I drag+drop the archive onto the extensions page, it fails. But the CircleCI artifact succeeds.

Something about the GitHub actions generated archive is different from the one we generate.

[Gudahtt]

Looks like the issue was that it got double-zipped. See actions/upload-artifact#39

When unzipping the outer archive, the inner one works just as before. This should be OK, as long as we ensure we're not submitting the double-zipped file to the Chrome/Firefox stores in the publishing step.

[Gudahtt]

LGTM!