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

Revert "Bump thatisuday/go-cross-build from 1.0.2 to 1.1.0" #56

Conversation

r0x0d
Copy link
Member

@r0x0d r0x0d commented Jul 26, 2023

Reverts #45

We need to keep the go-cross-build as 1.0.2 since there is a problem with the latest release introduced in v1.1.0. And as weird as it seems, v1.0.2 was the latest release for this action.

@r0x0d r0x0d self-assigned this Jul 26, 2023
@r0x0d r0x0d requested a review from andywaltlova July 26, 2023 13:36
@codecov-commenter
Copy link

Codecov Report

Patch and project coverage have no change.

Comparison is base (e0c5682) 61.16% compared to head (8993220) 61.16%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   61.16%   61.16%           
=======================================
  Files           5        5           
  Lines         327      327           
=======================================
  Hits          200      200           
  Misses        112      112           
  Partials       15       15           
Flag Coverage Δ
go-1.16 ?
go-1.20 61.16% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@r0x0d r0x0d merged commit 708c88e into main Jul 26, 2023
@r0x0d r0x0d deleted the revert-45-dependabot/github_actions/thatisuday/go-cross-build-1.1.0 branch July 26, 2023 13:47
@r0x0d r0x0d mentioned this pull request Aug 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants