Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🧹 Allow re-running the goreleaser job #4192

Merged
merged 1 commit into from
Jun 5, 2024
Merged

Conversation

czunker
Copy link
Contributor

@czunker czunker commented Jun 5, 2024

With this change, it can override the existing release files. This can help in case something goes wrong.

Copy link
Contributor

github-actions bot commented Jun 5, 2024

Test Results

3 047 tests  ±0   3 046 ✅ ±0   1m 19s ⏱️ -7s
  354 suites ±0       1 💤 ±0 
   26 files   ±0       0 ❌ ±0 

Results for commit 656dd08. ± Comparison against base commit ef14521.

@czunker czunker marked this pull request as ready for review June 5, 2024 05:42
@czunker czunker force-pushed the czunker/allow_override branch from 656dd08 to 231a909 Compare June 5, 2024 05:45
@chris-rock chris-rock requested a review from imilchev June 5, 2024 07:09
.goreleaser.yml Outdated
@@ -340,3 +340,6 @@ docker_manifests: # https://goreleaser.com/customization/docker_manifest/
- mondoo/{{ .ProjectName }}:latest-arm64v8-rootless
- mondoo/{{ .ProjectName }}:latest-armv6-rootless
- mondoo/{{ .ProjectName }}:latest-armv7-rootless
release:
replace_existing_artifacts: true
mode: keep-existing
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need this when we are replacing existing artifgacts?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. It is only about the release notes, not the artifacts:

What to do with the release notes in case there the release already exists.

Valid options are:

- keep-existing: keep the existing notes

- append: append the current release notes to the existing notes

- prepend: prepend the current release notes to the existing notes

- replace: replace existing notes

Default is keep-existing.

mode: append

https://goreleaser.com/customization/release/?h=replace_existing_artifacts#github

Perhaps not, now that I see the default.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed it.

With this change, it can override the existing release files.
This can help in case something goes wrong.

Signed-off-by: Christian Zunker <[email protected]>
@czunker czunker force-pushed the czunker/allow_override branch from 231a909 to c224a0f Compare June 5, 2024 07:53
@czunker czunker merged commit 68fc378 into main Jun 5, 2024
6 checks passed
@czunker czunker deleted the czunker/allow_override branch June 5, 2024 09:42
@github-actions github-actions bot locked and limited conversation to collaborators Jun 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants