chore(deps): update zricethezav/gitleaks-action action to v2 #166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.6.0
->v2.3.7
Release Notes
zricethezav/gitleaks-action (zricethezav/gitleaks-action)
v2.3.7
Compare Source
What's Changed
New Contributors
Full Changelog: gitleaks/gitleaks-action@v2.3.6...v2.3.7
v2.3.6
Compare Source
What's Changed
New Contributors
Full Changelog: gitleaks/gitleaks-action@v2...v2.3.6
v2.3.5
Compare Source
What's Changed
Full Changelog: gitleaks/gitleaks-action@v2...v2.3.5
v2.3.4
Compare Source
Full Changelog: gitleaks/gitleaks-action@v2.3.3...v2.3.4
v2.3.3
Compare Source
What's Changed
GITLEAKS_VERSION
env var by @spaze in https://github.com/gitleaks/gitleaks-action/pull/123New Contributors
Full Changelog: gitleaks/gitleaks-action@v2.3.2...v2.3.3
v2.3.2
Compare Source
What's Changed
Full Changelog: gitleaks/gitleaks-action@v2.3.1...v2.3.2
v2.3.1
Compare Source
What's Changed
Full Changelog: gitleaks/gitleaks-action@v2.3.0...v2.3.1
v2.3.0
Compare Source
What's Changed
Full Changelog: gitleaks/gitleaks-action@v2...v2.3.0
v2.2.1
Compare Source
What's Changed
Full Changelog: gitleaks/gitleaks-action@v2...v2.2.1
v2.2.0
Compare Source
What's Changed
You can now run scheduled runs with gitleaks-action. A scheduled gitleaks-action will scan the entire history of a repo. You can set up a scheduled run by adding
schedule
to theon
entry:Full Changelog: gitleaks/gitleaks-action@v2...v2.2.0
v2.1.4
Compare Source
What's Changed
v2.1.3
Compare Source
What's New
v2.1.2
Compare Source
v2.1.1
Compare Source
What's New
v2.1.0
Compare Source
What's new
v2.0.8
Compare Source
What's New
v2.0.7
Compare Source
What's Changed:
v2.0.6
Compare Source
What's New:
v2.0.5
Compare Source
What's New
base
andhead
refs are the same.v2.0.4
Compare Source
What's New
v2.0.3
Compare Source
What's New
eventJson.commits
for commit range rather thaneventJson.before
andeventJson.after
. This fixesinvalid revision range
on push event errors.v2.0.2
Compare Source
What's New
name
so this action can be published on the marketplacev2.0.1
Compare Source
What's New
GITLEAKS_ENABLE_SUMMARY
env var option to enable or disable Gitleaks-action job summaries (defaults to true)GITLEAKS_ENABLE_UPLOAD_ARTIFACT
env var option to enable or disable Gitleaks-action job artifact uploads (defaults to true)v2.0.0
Compare Source
What's Changed
Gitleaks-Action Version 2 brings a range of new features including:
1. On demand scans
You can now use
workflow_dispatch
events to trigger on demand gitleaks scans.2. Gitleaks report artifact uploads
Not much more to say here. Download reports when leaks are present. Pretty useful feature.
3. Powered by the latest version of Gitleaks
The latest version of gitleaks (v8.8.6 at the time of writing) has better performance, more configuration options, and is more accurate than the previous major version.
4. Job summaries
Easy to understand report of a Gitleaks job. If no leaks are detected you'll see:
If leaks are detected you'll see something like:
5. Faster job times
Gitleaks-Action Version 2 does not rely on Docker build anymore.
6. Pull Request Comments
If a leak is encountered during a pull request, gitleaks-action will comment on the line number and commit containing the secret.
What's fixed
git log
to determine the range of commits. Version 2 of gitleaks-action ensures that only relevent commits are scanned by leveraging Action context and GitHub's API.Getting started with Version 2
Getting a License-Key (ONLY FOR ORGANIZATION REPOS, USER ACCOUNTS DO NOT NEED A LICENSE KEY)
Before enabling Gitleaks-Action Version 2, you will need to obtain a gitleaks-action license key from gitleaks.io if you are using gitleaks within the context of an organization. If you are using gitleaks-aciton on a user account's repo, you do not need a license key. You can sign up for a free license key that will grant you access to use gitleaks-action on one repo. The free tier sign up link will take you to a google forms page where you can fill out your information. After filling out your information, you should receive an email similar to the one below.
NOTE: be patient with the free tier, the google forms API can be slow.
NOTE: 1 free license per account.
If you would like access to more repos for your organization or personal account, you can subscribe to one of the paid tiers which will grant you access to use Gitleaks-Action Version 2 on 10, 100, or 1000 repos.
Setting the
GITLEAKS_LICENSE
secretAfter getting a license key, head over to your github organization's or repo's settings and set
GITLEAKS_LICENSE
as a secret. Great! You can now run gitleaks-action v2:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.