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

feat: add goreleaser linting check and replace hardcoded version strings #598

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

AtomicFS
Copy link
Collaborator

@AtomicFS AtomicFS commented Feb 25, 2025

Update goreleaser configuration

  • update to v2
  • NOTE: some options we were still using there were deprecated

Replace hardcoded version strings

  • goreleaser already passes version based on git describe as ldflag along with commit and date (source: https://goreleaser.com/cookbooks/using-main.version/)
  • the main Taskfile now replicates the same exact behavior as goreleaser
  • we no longer have to keep these hardcoded strings in sync
  • when people build from source the version string is much more descriptive

@github-actions github-actions bot added testing Testing related github_actions Pull requests that update GitHub Actions code labels Feb 25, 2025
@AtomicFS AtomicFS changed the title test(lint): add goreleaser check feat: add goreleaser linting check and replace hardcoded version strings Feb 25, 2025
@github-actions github-actions bot added the go Pull requests that update Go code label Feb 25, 2025
- goreleaser already passes version based on git describe as ldflag
  along with commit and date
- source: https://goreleaser.com/cookbooks/using-main.version/
- the main Taskfile now replicates the same exact behavior as goreleaser
- we no longer have to keep these hardcoded strings in sync
- when people build from source the version string is much more
  descriptive

Signed-off-by: AtomicFS <[email protected]>
@AtomicFS AtomicFS force-pushed the test/add-goreleaser-check branch from 5ec848f to 068ab0f Compare February 25, 2025 16:14
@AtomicFS
Copy link
Collaborator Author

Failing on:

docker pull registry.dagger.io/engine:v0.16.1

With:

Error response from daemon: toomanyrequests: 429 Too Many Requests

This is a upstream issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
github_actions Pull requests that update GitHub Actions code go Pull requests that update Go code testing Testing related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant