Set up your GitHub Actions workflow with a specific version of Bun
Find a file
2024-05-27 18:47:06 +02:00
.github ci: remove cache test 2024-05-09 18:06:15 +02:00
dist [autofix.ci] apply automated fixes 2024-05-22 16:13:42 +00:00
src feat: add bun paths and url to output 2024-05-27 18:47:06 +02:00
.gitattributes Fix bunx (#18) 2023-09-11 12:37:45 -07:00
.gitignore Fix bunx (#18) 2023-09-11 12:37:45 -07:00
action.yml feat: add bun paths and url to output 2024-05-27 18:47:06 +02:00
bun.lockb fix: retry installing three times, add windows for testing (#72) 2024-04-02 11:24:51 +02:00
LICENSE chore: update package.json, license 2022-07-12 11:03:29 +02:00
package-lock.json [autofix.ci] apply automated fixes 2024-05-07 20:09:23 +00:00
package.json build: bump version 2024-05-07 22:08:47 +02:00
README.md feat: add input bun-version-file (#76) 2024-04-12 22:17:14 +02:00
tsconfig.json Various improvements and fixes to setup-bun (#40) 2023-11-17 15:58:17 -08:00

setup-bun

Download, install, and setup Bun in GitHub Actions.

Usage

- uses: oven-sh/setup-bun@v1
  with:
    bun-version: latest

Using version file

- uses: oven-sh/setup-bun@v1
  with:
    bun-version-file: ".bumrc"

Using a custom NPM registry

- uses: oven-sh/setup-bun@v1
  with:
    registry-url: "https://npm.pkg.github.com/"
    scope: "@foo"

If you need to authenticate with a private registry, you can set the BUN_AUTH_TOKEN environment variable.

- name: Install Dependencies
  env:
    BUN_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
  run: bun install --frozen-lockfile

Node.js not needed

In most cases, you shouldn't need to use the setup-node GitHub Action.

Inputs

Name Description Default Examples
bun-version The version of Bun to download and install. latest canary, 1.0.0, 1.0.x
bun-version-file The version of Bun to download and install from file. undefined .bumrc
registry-url Registry URL where some private package is stored. undefined "https://npm.pkg.github.com/"
scope Scope for private packages. undefined "@foo", "@orgname"
no-cache Disable caching of the downloaded executable. false true, false

Outputs

Name Description Example
cache-hit If the Bun executable was read from cache. true
bun-version The output from bun --version. 1.0.0
bun-revision The output from bun --revision. 1.0.0+822a00c4