Skip to content

feat(409): Add special handler for 409 HTTP errors when downloading certificates from GoDaddy #18

feat(409): Add special handler for 409 HTTP errors when downloading certificates from GoDaddy

feat(409): Add special handler for 409 HTTP errors when downloading certificates from GoDaddy #18

Triggered via pull request September 2, 2025 16:21
@irbyirby
synchronize #6
conflict-62981
Status Failure
Total duration 2m 54s
Artifacts 2
call-starter-workflow  /  ...  /  Set workflow variables from integration-manifest.json
8s
call-starter-workflow / call-assign-from-json-workflow / Set workflow variables from integration-manifest.json
call-starter-workflow  /  ...  /  Grep TODO and License Headers
4s
call-starter-workflow / call-create-github-release-workflow / call-check-file-action / Grep TODO and License Headers
call-starter-workflow  /  Detect Primary Language
8s
call-starter-workflow / Detect Primary Language
call-starter-workflow  /  Check for .goreleaser file
4s
call-starter-workflow / Check for .goreleaser file
call-starter-workflow  /  setup_platforms
5s
call-starter-workflow / setup_platforms
call-starter-workflow  /  ...  /  create-github-release-workflow
7s
call-starter-workflow / call-create-github-release-workflow / create-github-release-workflow
call-starter-workflow  /  ...  /  Use private doctool action in public repository
call-starter-workflow / call-generate-readme-workflow / Use private doctool action in public repository
call-starter-workflow  /  ...  /  Configure branch protection
call-starter-workflow / call-repository-configuration-workflow / Configure branch protection
call-starter-workflow  /  ...  /  Updating repository settings
call-starter-workflow / call-repository-configuration-workflow / Updating repository settings
call-starter-workflow  /  ...  /  update-catalog-entry
call-starter-workflow / call-update-catalog-workflow / update-catalog-entry
call-starter-workflow  /  ...  /  create-github-release
4s
call-starter-workflow / call-create-github-release-workflow / create-github-release
call-starter-workflow  /  ...  /  Get Release Properties
call-starter-workflow / call-container-build-and-release-workflow / Get Release Properties
call-starter-workflow  /  ...  /  setup
call-starter-workflow / call-container-build-and-release-workflow / setup
call-starter-workflow  /  ...  /  Create PR from release branch to main
call-starter-workflow / call-post-release-workflow / Create PR from release branch to main
call-starter-workflow  /  ...  /  dotnet-build-and-release
2m 30s
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release
call-starter-workflow  /  ...  /  Build and Possibly release maven hpi artifact
call-starter-workflow / call-maven-build-and-release-workflow / Build and Possibly release maven hpi artifact
call-starter-workflow  /  ...  /  run-goreleaser
call-starter-workflow / call-go-build-and-release-workflow / run-goreleaser
Matrix: call-starter-workflow / call-container-build-and-release-workflow / Build Containers
Waiting for pending jobs
call-starter-workflow  /  ...  /  merge
call-starter-workflow / call-container-build-and-release-workflow / merge
Fit to window
Zoom out
Zoom in

Annotations

1 error, 10 warnings, and 1 notice
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyEnrollment.cs#L317
Do not use Assert.True() to check if a value exists in a collection. Use Assert.Contains instead. (https://xunit.net/xunit.analyzers/rules/xUnit2017)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyEnrollment.cs#L316
Do not use Assert.True() to check if a value exists in a collection. Use Assert.Contains instead. (https://xunit.net/xunit.analyzers/rules/xUnit2017)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyCAPlugin.cs#L234
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyCAPlugin.cs#L183
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyEnrollment.cs#L163
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyEnrollment.cs#L237
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyCAPlugin.cs#L97
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyEnrollment.cs#L89
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyCAPlugin.cs#L136
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Artifacts

Produced during runtime
Name Size Digest
licenselogs Expired
146 Bytes
sha256:6dd548bc72196ceff949a59eb44cf7ae211260eb463be4990edae168090bce64
todologs Expired
140 Bytes
sha256:79713601c87c802082e0fbfa838fcc1baf4d093dfb00b1df3ff4ddb738cf944a