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

Go Build & Test GHA fails while running goreleaser v1.19.0 #159

Closed
pashagolub opened this issue Jul 4, 2023 · 0 comments · Fixed by #160
Closed

Go Build & Test GHA fails while running goreleaser v1.19.0 #159

pashagolub opened this issue Jul 4, 2023 · 0 comments · Fixed by #160
Assignees
Labels
bug github_actions Pull requests that update GitHub Actions code

Comments

@pashagolub
Copy link
Collaborator

/opt/hostedtoolcache/goreleaser-action/1.19.0/x64/goreleaser release --snapshot --skip-publish --rm-dist
Flag --rm-dist has been deprecated, please use --clean instead
  • starting release...
  • loading config file                              file=.goreleaser.yml
  ⨯ release failed after 0s                  error=yaml: unmarshal errors:
  line 17: field replacements not found in type config.Archive
  line 45: field replacements not found in type config.NFPM
Error: The process '/opt/hostedtoolcache/goreleaser-action/1.19.0/x64/goreleaser' failed with exit code 1

New version removed deprecated sections and command-line options: https://goreleaser.com/deprecations/#expired-deprecation-notices_1

@pashagolub pashagolub self-assigned this Jul 4, 2023
@pashagolub pashagolub added bug github_actions Pull requests that update GitHub Actions code labels Jul 4, 2023
@pashagolub pashagolub linked a pull request Jul 4, 2023 that will close this issue
pashagolub added a commit that referenced this issue Jul 4, 2023
…1.19

[+] add support for goreleaser v1.19, fixes #159
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug github_actions Pull requests that update GitHub Actions code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant