Connect repository
Add the GitHub repo URL so ReleaseReady can map webhook events and execution requests to the right project.
Release Readiness Platform
ReleaseReady reduces CI configuration overhead for Playwright JavaScript and TypeScript repos by centralizing triggers, execution, result ingestion, and checklist visibility.
ReleaseReady
Platform Overview
Checks Passed
31
Blocked
2
Missing
1
| Checklist run | Status | QA |
|---|---|---|
| Regression suite | Passed | Complete |
| Smoke tests | Passed | Complete |
| Rollback plan | Blocked | Missing |
Built for teams that want confidence in every release
Quickstart
Strong onboarding matters for dev tools. Connect a repo, keep your existing flow, and get to the first successful run quickly.
Add the GitHub repo URL so ReleaseReady can map webhook events and execution requests to the right project.
Use the project webhook for PR-driven automation or start with a manual run while you validate setup.
Delegate execution to your configured runner or let ReleaseReady execute the repo directly when runner mode is not enabled.
Inspect one run record with status, output, checklist context, and runner metadata when available.
Before / After YAML
Show the value in seconds: ReleaseReady reduces CI configuration overhead for Playwright JS/TS repos and keeps teams focused on test failures instead of workflow plumbing.
Before
Verbose GitHub Actions workflows accumulate checkout, cache, browser install, sharding, artifact, and notification logic.
After
Keep the trigger, let ReleaseReady orchestrate the run, result handling, and checklist visibility. The technical story stays credible because the product already supports webhook, manual, and runner-result flows.
Before
name: playwright-ci
on:
pull_request:
branches: [main]
push:
branches: [main]
jobs:
e2e:
runs-on: ubuntu-latest
timeout-minutes: 30
strategy:
fail-fast: false
matrix:
shard: [1, 2, 3, 4]
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 20
cache: npm
- name: Install dependencies
run: npm ci
- name: Install Playwright browsers
run: npx playwright install --with-deps
- name: Run smoke tests
run: npx playwright test --grep @smoke --shard=${{ matrix.shard }}/4
- name: Upload playwright report
if: always()
uses: actions/upload-artifact@v4
with:
name: playwright-report-${{ matrix.shard }}
path: playwright-report/
- name: Upload blob report
if: always()
uses: actions/upload-artifact@v4
with:
name: blob-report-${{ matrix.shard }}
path: blob-report/
merge-reports:
needs: e2e
runs-on: ubuntu-latest
if: always()
steps:
- uses: actions/download-artifact@v4
- run: node scripts/merge-playwright-reports.js
- run: node scripts/post-status-to-slack.jsAfter
name: release-ready
on:
pull_request:
types: [opened, synchronize, reopened, ready_for_review]
jobs:
notify-release-ready:
runs-on: ubuntu-latest
steps:
- name: Let ReleaseReady orchestrate execution
env:
RELEASEREADY_WEBHOOK_URL: ${{ vars.RELEASEREADY_WEBHOOK_URL }}
RELEASEREADY_WEBHOOK_SECRET: ${{ secrets.RELEASEREADY_WEBHOOK_SECRET }}
RELEASEREADY_PLAYWRIGHT_IMAGE: mcr.microsoft.com/playwright:v1.58.0-noble
RELEASEREADY_TEST_COMMAND: npm test
run: |
set -euo pipefail
RELEASEREADY_WEBHOOK_URL="$(printf '%s' "$RELEASEREADY_WEBHOOK_URL" | tr -d '\r\n')"
RELEASEREADY_WEBHOOK_SECRET="$(printf '%s' "$RELEASEREADY_WEBHOOK_SECRET" | tr -d '\r\n')"
RELEASEREADY_SIGNATURE="sha256=$(openssl dgst -sha256 -hmac "$RELEASEREADY_WEBHOOK_SECRET" -binary "$GITHUB_EVENT_PATH" | xxd -p -c 256)"
RESPONSE_FILE="$(mktemp)"
STATUS_CODE="$(curl -sS -o "$RESPONSE_FILE" -w "%{http_code}" -X POST "$RELEASEREADY_WEBHOOK_URL" -H "X-Hub-Signature-256: $RELEASEREADY_SIGNATURE" -H "X-GitHub-Event: pull_request" -H "X-ReleaseReady-Playwright-Image: $RELEASEREADY_PLAYWRIGHT_IMAGE" -H "X-ReleaseReady-Command: $RELEASEREADY_TEST_COMMAND" -H "Content-Type: application/json" --data-binary "@$GITHUB_EVENT_PATH")"
cat "$RESPONSE_FILE"
if [ "$STATUS_CODE" -ge 400 ]; then
echo "\nReleaseReady webhook failed with HTTP $STATUS_CODE" >&2
exit 1
fi
# ReleaseReady handles:
# - project mapping
# - trigger orchestration
# - delegated runner execution or direct execution
# - result ingestion
# - checklist run visibilityRelease decisions are often fragmented across tools. Teams need a dependable way to verify readiness before deployment.
Automated tests can look green while required approvals, regression checks, and release notes are still missing.
Teams track readiness in docs, spreadsheets, and Slack threads, making validation hard to trust and easy to miss.
Engineering and QA often evaluate different signals, so release status depends on assumptions instead of clear criteria.
Missing checks are frequently discovered during deployment or after production rollout when risk is highest.
Solution
ReleaseReady becomes the control layer before deployment. Define what ready means, evaluate conditions automatically, and expose a single status for the team.
ReleaseReady
Platform Overview
Checks Passed
31
Blocked
2
Missing
1
| Checklist run | Status | QA |
|---|---|---|
| Regression suite | Passed | Complete |
| Smoke tests | Passed | Complete |
| Rollback plan | Blocked | Missing |
Set release policy once, ingest execution signals continuously, and make ship decisions obvious.
Create checklists, validations, and approval requirements for each project and release type.
Ingest test runs and execution outputs from QA suites, CI pipelines, and external runners.
See whether a release is ready, blocked, or missing critical validations in one clear status.
Everything your team needs to answer one question: are we actually ready to ship?
Structured validation requirements before deployment.
Track each execution of release validation clearly.
Collect automated run results from external runners or CI workflows.
Prevent shipping when critical checks are incomplete.
Understand what passed, failed, or is still missing.
Manage readiness by project and release context.
A clean, project-based workspace showing checklist runs, execution outcomes, and a clear readiness state at every stage.
ReleaseReady
Platform Overview
Checks Passed
31
Blocked
2
Missing
1
| Checklist run | Status | QA |
|---|---|---|
| Regression suite | Passed | Complete |
| Smoke tests | Passed | Complete |
| Rollback plan | Blocked | Missing |
Need visibility into execution results and release validation without growing YAML maintenance overhead.
Need safer gates before deployment while keeping current trigger flows intact.
Need clear readiness status without chasing updates across CI, docs, and messaging tools.
Need lightweight release control for Playwright repos without building custom orchestration first.
Use ReleaseReady to keep Playwright setup practical, preserve your current working flows, and get implementation guidance from day one.