Topic

#ci

Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.

#ci

3Shown loot

3Shown articles

8Linked neighbor tags

Topic paths

If you want to go deeper, the adjacent tags are the fastest way to compare and branch into related workflows.

Loot

More from this topic

Explore all loot

Make Vercel CLI 55 project linking safe for CI agents

#vercel #cli+3

Vercel CLI 55 changes how vercel link, deploy, pull, dev, and git connect resolve teams and projects. CI and agent workflows should pass --team/--scope or set VERCELORGID and VERCELPROJECTID before upgrading, because --yes no longer selects a team automatically. Use this as an upgrade checkpoint before moving CI, coding agents, or deployment scripts to Vercel CLI 55. The linking flow now resolves the team first and searches projects inside that team, which makes project discovery faster but removes an old implicit behavior: --yes confirms prompts, but it does not choose a team. For promptless runs, set VERCELORGID and VERCELPROJECTID, or pass --team/--scope explicitly. If a command has multiple possible teams and no explicit signal, non-interactive runs can fail with actionrequired: missingscope before creating or touching a link. That is useful for safety, but only if your automation expects it.

Free

Review open

@ZachasADMIN

Open loot

Run Playwright tests faster on Vercel with Endform

#endform #vercel+3

Endform runs existing Playwright suites on isolated cloud runners and plugs the result into Vercel preview and production deployments. Endform is a managed Playwright test runner for Vercel teams that want deployment checks without building their own browser-runner fleet. It is useful when a suite is slow because tests run serially, collide on shared state, or need trace history across preview deployments. Vercel's Marketplace changelog says Endform can run each test on its own isolated machine, link pass/fail checks to Vercel deployments, keep full Playwright traces, and charge by test runtime. Endform's docs add the important setup caveat: tests run remotely, so the target app must be reachable by the remote runners or proxied through Endform's local-network option. Best fit Vercel apps with Playwright suites that slow down preview deploys. Teams that want deployment checks tied to traces and historical runs. SaaS products where flaky E2E tests delay releases. Projects that already use @playwright/test and want less CI plumbing. Check before using Confirm pricing and runtime limits for your test volume. Make sure each test is independent enough to run in parallel. Check how preview deployment protection, secrets, and test accounts are handled. Validate that remote runners can reach the app or configure the proxy path. Keep destructive tests away from production data.

Free

Review open

@ZachasADMIN

Open loot

Verify JDK Downloads in GitHub Actions with setup-java 5.5

#GitHub Actions #Java+3

GitHub Actions setup-java 5.5 adds optional cryptographic signature verification for downloaded JDKs, plus Tencent Kona support and Maven workflow fixes. Use this when Java CI needs stronger supply-chain checks without replacing the standard setup-java action. Enable verify-signature: true for supported distributions such as Temurin and Microsoft, pin the action to v5.5.0 or its full commit SHA, and fail fast when a distribution cannot verify signatures instead of silently accepting an unchecked JDK download. This is a TOOL candidate, not a broad news post: it helps teams harden Java workflows, but it does not materially change the whole developer platform.

Free

Review open

@ZachasADMIN

Open loot

Blog

#ci

More from this topic

Make Vercel CLI 55 project linking safe for CI agents

Run Playwright tests faster on Vercel with Endform

Verify JDK Downloads in GitHub Actions with setup-java 5.5

Related reads

npm v12 turns risky install behavior into explicit opt-in

Stop coverage drops before merge: GitHub adds code coverage rulesets

Audit GitHub Actions self-hosted runners before the July brownouts