Skip to content

feat: add EXCLUDE_AUTHORS env var for excluding users from conflict detection #62

feat: add EXCLUDE_AUTHORS env var for excluding users from conflict detection

feat: add EXCLUDE_AUTHORS env var for excluding users from conflict detection #62

Triggered via pull request May 12, 2026 15:45
@zkoppertzkoppert
closed #89
Status Success
Total duration 2m 35s
Artifacts 1

release.yml

on: pull_request_target
release  /  create_release
22s
release / create_release
release  /  release_goreleaser
release / release_goreleaser
release  /  release_image
1m 43s
release / release_image
release  /  release_discussion
14s
release / release_discussion
release  /  publish_release
14s
release / publish_release
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
release / release_discussion
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: abirismyname/create-discussion@c2b7c825241769dda523865ae444a879f6bbd0e0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
release / release_image
Please check that the "artifact-metadata:write" permission has been included
release / release_image
Failed to create storage record: Error: Failed to persist storage record: no artifacts found - https://docs.github.com/rest/orgs/artifact-metadata#create-artifact-metadata-storage-record
Legacy key/value format with whitespace separator should not be used: Dockerfile#L5
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Artifacts

Produced during runtime
Name Size Digest
github-community-projects~pr-conflict-detector~NOE7ML.dockerbuild Expired
94.7 KB
sha256:844fef365dbcbe6e54019b2225b2c0214bc5645a3d68c719286509e50cf51487