v1.2.0

• Do not call setSecret on any unmasked secrets (#17)

Full Changelog: v1.1.3...v1.2.0

v1.1.3

• Use Node 20 by @rgharris in #15
• Update version in README examples by @watsonian in #13

Full Changelog: v1.1.2...v1.1.3

v1.1.2

• Adds support for Service Account tokens

v1.1.1

• Updates @actions/core to get update saveState and setOutput functions

Added support for Personal Tokens

A Doppler Personal Token provides read/write access to every Project and Config accessible for that account and should only be used when necessary. The doppler-project and doppler-config inputs must be provided when using a Personal Token.

- uses: dopplerhq/secrets-fetch-action@v1.1.0
      id: doppler
      with:
        doppler-token: ${{ secrets.PERSONAL_DOPPLER_TOKEN }}
        doppler-project: auth-api
        doppler-config: ci-cd

Initial release

Securely inject Doppler secrets into your GitHub Actions.

• Reference secrets using step outputs: ${{ steps.doppler.outputs.API_TOKEN }}
• Optionally inject secrets as environment variables

Full Changelog: https://github.com/DopplerHQ/secrets-fetch-action/commits/v1.0.0