You're viewing an older version of this GitHub Action. Do you want to see the latest version instead?
GitHub Action
browserslist-update-action
v1.5.0
A Github Action that runs npx browserslist@latest --update-db
on a repository and proposes a pull request to merge updates.
name: Update Browserslist database
on:
schedule:
- cron: '0 2 1,15 * *'
permissions:
contents: write
pull-requests: write
jobs:
update-browserslist-database:
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v3
with:
fetch-depth: 0
- name: Configure git
run: |
git config --global user.email "action@github.com"
git config --global user.name "GitHub Action"
- name: Update Browserslits database and create PR if applies
uses: c2corg/browserslist-update-action@v1
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
branch: browserslist-update
base_branch: main
commit_message: 'build: update Browserslist db'
title: 'build: update Browserslist db'
body: Auto-generated by [browserslist-update-action](https://github.com/c2corg/browserslist-update-action/)
Inputs with defaults are optional.
Name | Description | Default |
---|---|---|
github_token | GITHUB_TOKEN (contents: write , pull-requests: write ) or a repo scoped Personal Access Token (PAT). |
GITHUB_TOKEN |
branch | The pull request branch name. | browserslist-update |
base_branch | The target branch into which the pull request will be merged. | master |
directory | For monorepos, the directory to switch to when running action | . |
commit_message | The message to use when committing changes. | Update caniuse database |
title | The title of the pull request. | 📈 Update caniuse database |
body | The body of the pull request. | Caniuse database has been updated. Review changes, merge this PR and have a 🍺. |
One will usually run this action on a cron basis (say, every day or week)
src/types
folder contains generated type definitions based on queries. Run npm run types
to update.
npm run lint
npm run build
npm run pack
Or shortly
npm run all
Then bump version number in package.json
and package-lock.json
. Push commits.
Keep a major version tag synchronized with updates, e.g. if you publish version v2.0.3
, then a v2
branch should be positioned at the same location.