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

Fix release version detection #722

Merged
merged 1 commit into from
Apr 8, 2024
Merged

Conversation

TheAssassin
Copy link
Contributor

Should fix build issues like in #721.

@mgmax mgmax merged commit 4054819 into t-oster:master Apr 8, 2024
6 checks passed
@mgmax
Copy link
Collaborator

mgmax commented Apr 8, 2024

Thanks for the improvement. I'm not sure if this really solves the root cause. We will probably have the same issue if someone clones and builds locally. Looks like GitHub releases is only intended for building "release" versions and not every single commit?

@TheAssassin TheAssassin deleted the fix-checkinstall branch April 8, 2024 20:18
@TheAssassin
Copy link
Contributor Author

People are indeed affected locally as well. This was specifically meant to "fix" the problem on the CI for now. I know that @jnweiger has had this problem locally once already.

mgmax added a commit to mgmax/VisiCut that referenced this pull request May 25, 2024
The old workaround is no longer needed, now that tthe issue has been proper fixed in b407646

Revert "Fix release version detection (t-oster#722)"

This reverts commit 4054819.
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