dev-release workflow (parcel-bundler/parcel)
The dev-release workflow from parcel-bundler/parcel, explained and optimized by Latchkey.
A
CI health: A - excellent
Run this on Latchkey for self-healing, caching, and up to 58% lower cost.
Grade your own workflow free or run it on Latchkey →What it does
This is the dev-release workflow from the parcel-bundler/parcel repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
workflow (.yml)
# This workflow builds and releases all packages with a dev dist tag. Once published,
# the packages can be installed to streamline the testing and validation of changes, both
# locally and within CI, that have not yet been approved or merged into the main branch.
name: dev-release
on:
workflow_dispatch:
jobs:
build-and-release:
name: Build and release dev
uses: ./.github/workflows/release.yml
secrets: inherit
with:
profile: canary
release-command: yarn dev:release
type: dev
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
# This workflow builds and releases all packages with a dev dist tag. Once published, # the packages can be installed to streamline the testing and validation of changes, both # locally and within CI, that have not yet been approved or merged into the main branch. name: dev-release on: workflow_dispatch: jobs: build-and-release: timeout-minutes: 30 name: Build and release dev uses: ./.github/workflows/release.yml secrets: inherit with: profile: canary release-command: yarn dev:release type: dev
What changed
- Add a job timeout so a hung step cannot burn hours of runner time.
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.