4bdf2e9ba6
Bumps [actions/dependency-review-action](https://github.com/actions/dependency-review-action) from 2 to 3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/dependency-review-action/releases">actions/dependency-review-action's releases</a>.</em></p> <blockquote> <h2>3.0.0</h2> <h2>Breaking Changes</h2> <p>By default the action now expects <a href="https://spdx.org/licenses/">SPDX-compliant licenses</a> everywhere. If you were previously using license names in the allow or deny lists make sure they're valid!</p> <h2>What's Changed</h2> <h3>Support for external configuration files</h3> <p>You can now specify a <a href="https://github.com/actions/dependency-review-action/#configuration-file">configuration file external to your repository</a>. This allows organizations to have a single configuration file for all their repos.</p> <h3>Broader license support</h3> <p>We've added support for a much broader set of project licenses by using GitHub's <a href="https://docs.github.com/en/rest/licenses">Licenses API</a>.</p> <h3>SPDX Compliance</h3> <p>All of our license-related code now expects <a href="https://spdx.org/licenses/">SPDX-compliant licenses or expressions</a>. This allows us to standardize on a license naming scheme that already supports <code>OR</code>/<code>AND</code> expressions.</p> <h3>Disable individual checks</h3> <p>You can now use the boolean options <code>license-check</code> and <code>vulnerability-check</code> to disable either one of the checks. More information in <a href="https://github.com/actions/dependency-review-action/#configuration-options">our configuration options</a>.</p> <h2>Thanks</h2> <p>Contributors for this release include:</p> <ul> <li><a href="https://github.com/cnagadya"><code>@cnagadya</code></a></li> <li><a href="https://github.com/courtneycl"><code>@courtneycl</code></a></li> <li><a href="https://github.com/ericcornelissen"><code>@ericcornelissen</code></a></li> <li><a href="https://github.com/elireisman"><code>@elireisman</code></a></li> <li><a href="https://github.com/hmaurer"><code>@hmaurer</code></a></li> </ul> <p>Thanks everyone! <strong>Full Changelog</strong>: <a href="https://github.com/actions/dependency-review-action/compare/v2...v3.0.0">https://github.com/actions/dependency-review-action/compare/v2...v3.0.0</a></p> <h2>2.5.1</h2> <p>Adding some quality-of-life improvements to the local development experience. You can now pass a flag to the <code>scripts/scan_pr</code> script using the <code>-c/--config-file</code> flags to use an external configuration file:</p> <p>Example:</p> <pre><code> scripts/scan_pr https://github.com/actions/dependency-review-action/pull/294 </code></pre> <h2>2.5.0</h2> <p>Fallback on GitHub Licenses API data for missing Dependency Review API Licenses. This should improve our license coverage.</p> <h2>2.4.1</h2> <p>This patch release fixes the bugs below:</p> <ul> <li>Display the dependency name instead of the manifest name in the detailed list of dependents.</li> <li>Fix an issue where undefined GHSAs would remove filter out all changes.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
---|---|---|
.github | ||
cmd | ||
internal | ||
pkg | ||
scripts | ||
www | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.gitleaks.toml | ||
.golangci.yaml | ||
.goreleaser.yaml | ||
.grype.yaml | ||
.mailmap | ||
CONTRIBUTING.md | ||
Dockerfile | ||
EULA.md | ||
go.mod | ||
go.sum | ||
LICENSE.md | ||
main_test.go | ||
main.go | ||
README.md | ||
SECURITY.md | ||
Taskfile.yml | ||
USERS.md | ||
vercel.json |
GoReleaser
Deliver Go binaries as fast and easily as possible.
GoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. All that wrapped in your favorite CI.
Get GoReleaser
Documentation
Documentation is hosted live at https://goreleaser.com
Community
You have questions, need support and or just want to talk about GoReleaser?
Here are ways to get in touch with the GoReleaser community:
You can find the links above and all others here.
Code of Conduct
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. We appreciate your contribution. Please refer to our contributing guidelines for further information.
Badges
Sponsors
Does your company use goreleaser? Help keep the project bug-free and feature rich by sponsoring the project.
Backers
Love our work and community? Become a backer.
Contributors
This project exists thanks to all the people who contribute. [Contribute].