Repair wp/5.5 branch Actions: Add timeouts to CI jobs that have none

[desrosj]

What?

Adds timeout-minutes to the CI jobs on this branch that don't have one:

File	Job	Check	Minutes	Trunk
bundle-size.yml	build	Compressed Size Check	30	15
create-block.yml	build	Create Block	20	10
end2end-test.yml	admin-1	Admin - 1	45	none
end2end-test.yml	admin-2	Admin - 2	45	none
end2end-test.yml	admin-3	Admin - 3	45	none
end2end-test.yml	admin-4	Admin - 4	45	none
static-checks.yml	check	Static Analysis All	30	30
unit-test.yml	unit-php	PHP	20	20

One more job gets a timeout further up the stack, in the PR that adds it:

• unit-test.yml phpcs (PHP coding standards): 20, added in Repair wp/5.5 branch Actions: Run PHP coding standards on the runner instead of inside wp-env #517, the PR that creates the job.

Why?

Without timeout-minutes, a stuck job runs until GitHub's 360-minute default. On 2026-10-07, Playwright shards on wp/7.1–wp/6.2 hung for 2.3–3 hours in playwright install --with-deps while an Ubuntu apt mirror was degraded. Trunk added job timeouts for this in WordPress@27f57c9 (WordPress#80801).

This branch doesn't run --with-deps, so here the timeouts guard against hangs in general.

How?

Uses trunk's values from WordPress#80801 and WordPress@9ee17a7 (WordPress#46510) where this branch's job durations fit under them, and raises them where they don't, because on these branches every job builds and installs on its own without trunk's shared build and apt cache:

• Compressed Size Check: Runs on other wp/X.Y branches have taken 14.2 minutes, so trunk's 15 is too tight.
• Create Block: Runs on other wp/X.Y branches have taken 11.1 minutes, so trunk's 10 would cut them off.
• Admin - 1: CI: Add job timeouts to E2E, static checks, bundle size, and create block WordPress/gutenberg#80801 doesn't cover the Puppeteer e2e jobs. The slowest run took 17.8 minutes.
• Admin - 2: CI: Add job timeouts to E2E, static checks, bundle size, and create block WordPress/gutenberg#80801 doesn't cover the Puppeteer e2e jobs. The slowest run took 17.8 minutes.
• Admin - 3: CI: Add job timeouts to E2E, static checks, bundle size, and create block WordPress/gutenberg#80801 doesn't cover the Puppeteer e2e jobs. The slowest run took 17.8 minutes.
• Admin - 4: CI: Add job timeouts to E2E, static checks, bundle size, and create block WordPress/gutenberg#80801 doesn't cover the Puppeteer e2e jobs. The slowest run took 17.8 minutes.

Each timeout-minutes goes next to the job's runs-on. There is no step-level timeout on dependency installs: successful installs have taken up to 21 minutes.

Use of AI Tools

This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.

🤖 Generated with Claude Code