Releases: DopplerHQ/secrets-fetch-action
Releases · DopplerHQ/secrets-fetch-action
v1.3.0
What's Changed
- New OIDC auth method by @rgharris in #20
- Bump version in README and update masking description by @watsonian in #18
- Fix broken GitHub app link by @nmanoogian in #19
Full Changelog: v1.2.0...v1.3.0
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 updatesaveState
andsetOutput
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/[email protected]
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