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

zig: fix update-check #44810

Merged
merged 1 commit into from Jul 3, 2023
Merged

zig: fix update-check #44810

merged 1 commit into from Jul 3, 2023

Conversation

Bnyro
Copy link
Contributor

@Bnyro Bnyro commented Jul 3, 2023

Testing the changes

  • I tested the changes in this PR: YES

cc @ifreund

@ifreund
Copy link
Contributor

ifreund commented Jul 3, 2023

I don't rely on update check to know when a new zig release is coming. Packaging a new zig release will likely need to happen in step with LLVM packaging anyway.

I have no objections to this existing though.

@Bnyro
Copy link
Contributor Author

Bnyro commented Jul 3, 2023

Yes, I agree in general. You're probably aware of new zig releases before they are published anyways :)
However, I think it'd be nice to have the update check work anyways, won't have any negative impact :)

@Chocimier Chocimier merged commit 738f5ca into void-linux:master Jul 3, 2023
8 checks passed
@Bnyro Bnyro deleted the zig branch July 7, 2023 05:58
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.

None yet

3 participants