chore: bump goselect to 0.1.3#206
Closed
chrisdalke wants to merge 1 commit intobugst:masterfrom
Closed
Conversation
chrisdalke
force-pushed
the
chore/bump-goselect-0.1.3
branch
from
372f292 to
e8938fa
Compare
Author
|
Just noticed this is duplicated by #203. I can close mine if that PR is merged, thanks. |
Closed
6 tasks
Contributor
|
Appreciate that it might be easier to bump, but github.com//pull/149 to remove goselect might be worth doing, since goselect was archived by the owner on Apr 10, 2025. |
Member
|
Thanks for your support! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bump goselect to 0.1.3; this version of goselect supports loong64.
I'm using go-serial indirectly via gomavlib on a project which requires loong64, so this will help add support for that compilation target!