CI/CD Pipeline - Chrome Web Store workflow (NirmalScaria/le-git-graph)

The CI/CD Pipeline - Chrome Web Store workflow from NirmalScaria/le-git-graph, explained and optimized by Latchkey.

CI health: C - fair

Point runs-on at Latchkey and get run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →

Source: NirmalScaria/le-git-graph.github/workflows/chrome-release.ymlLicense MITView source

What it does

This is the CI/CD Pipeline - Chrome Web Store workflow from the NirmalScaria/le-git-graph 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)

name: CI/CD Pipeline - Chrome Web Store
on:
  push:
    branches:
    - chrome-release
  workflow_dispatch:
jobs:
  publish-chrome-web-store:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
        with:
          ref: chrome-release
        name: Checkout the repository
      - run: zip -r chrome-release.zip *
        name: Zip the extension
      - uses: actions/upload-artifact@v4
        name: Store the zip artifact
        with:
          name: chrome-release
          path: chrome-release.zip
      - name: Upload and Release
        uses: mnao305/chrome-extension-upload@v5.0.0
        with:
          file-path: chrome-release.zip
          extension-id: ${{ secrets.CWS_EXTENSION_ID }}
          client-id: ${{ secrets.CWS_CLIENT_ID }}
          client-secret: ${{ secrets.CWS_CLIENT_SECRET }}
          refresh-token: ${{ secrets.CWS_REFRESH_TOKEN }}
          publish: true

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: CI/CD Pipeline - Chrome Web Store
on:
  push:
    branches:
    - chrome-release
  workflow_dispatch:
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  publish-chrome-web-store:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v3
        with:
          ref: chrome-release
        name: Checkout the repository
      - run: zip -r chrome-release.zip *
        name: Zip the extension
      - uses: actions/upload-artifact@v4
        name: Store the zip artifact
        with:
          name: chrome-release
          path: chrome-release.zip
      - name: Upload and Release
        uses: mnao305/chrome-extension-upload@v5.0.0
        with:
          file-path: chrome-release.zip
          extension-id: ${{ secrets.CWS_EXTENSION_ID }}
          client-id: ${{ secrets.CWS_CLIENT_ID }}
          client-secret: ${{ secrets.CWS_CLIENT_SECRET }}
          refresh-token: ${{ secrets.CWS_REFRESH_TOKEN }}
          publish: true

What changed

Run on Latchkey managed runners with one line (runs-on), which apply the fixes below automatically and self-heal transient failures. This example uses latchkey-small; pick the runner size that fits the job.
Cancel superseded runs when a branch or PR gets a newer push.
Add a job timeout so a hung step cannot burn hours of runner time.

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow

actions/checkout actions/upload-artifact