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

Install on linux fails with 1.43.3 #1590

Closed
jbockler opened this issue May 13, 2024 · 2 comments
Closed

Install on linux fails with 1.43.3 #1590

jbockler opened this issue May 13, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@jbockler
Copy link

jbockler commented May 13, 2024

Our CI that does the bearer scan fails since the release of 1.43.3, because it can not install bearer.

Description & Reproduction

We are using the install script for bearer:
curl -sfL https://raw.githubusercontent.com/Bearer/bearer/main/contrib/install.sh | sh

Platform: linux/amd64

Expected Behavior

Bearer should be installed.

Actual Behavior

Output:

Bearer/bearer info Checking dependencies...
git version 2.25.1
Bearer/bearer info checking GitHub for latest tag
Bearer/bearer info found version: 1.43.3 for v1.43.3/linux/amd64

And then the install script exists

Possible Fix

I have seen that the Github release only contains the tarballs for darwin. Is this intentional?

Your Environment

  • Operating System and version: Ubuntu
@jbockler jbockler added the bug Something isn't working label May 13, 2024
@gotbadger
Copy link
Contributor

gotbadger commented May 14, 2024

@jbockler We had an issue yesterday where goreleaser somehow made a pre-release public. These pre releases do not build with all targets which would cause the install script to fail. We didnt notice this immediately and we have since released the full build (think about an hour after this issue was opened).

I've verifed this on a linux/amd64 ubuntu:18.04 docker image and it appears to be working now. Let me know if you are still having issues and I can investigate more.

FYI we are currently investigating what happened and guarding a bit more against this with changes in #1591

@jbockler
Copy link
Author

@gotbadger Thanks for the update and the quick resolution! Everything seems to be working fine on my end now as well, so I'm closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants