-
Notifications
You must be signed in to change notification settings - Fork 110
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
Please post a new release #44
Comments
I think we have one issue outstanding (#43) that we'd like to get in first. |
I would be happy if #45 makes it in as well (: |
I don't have permission to make a release, you'll have to bug @Osspial or @goddessfreya or @francesca64 |
I unfortunately was never given permission... I reached out to @Osspial in the hopes of getting that amended, but no luck so far. @goddessfreya is also MIA on Github (hope she's doing well!), but I haven't tried contacting her directly. I will pursue this further. @dvc94ch would you like release permission as well? I doubt we're ever going to have the problem of having too much autonomy, though I guess I'm not yet in any position to be making promises. |
That would be great, thanks for looking into it |
Did we end up finding anybody to do this, or did everybody end up disappearing? 👀 |
@Jasper-Bekkers I certainly won't be disappearing, and I've successfully made contact, so I'll likely be able to resolve this soon. @Osspial is active as well, so you can always try your luck at notification roulette, but her inbox is surely flooded. |
@francesca64 That's good to hear 😊🥳 |
I’ve published patch releases of |
We've been running into a bunch of issue here last night when collaborating with somebody, that we've submitted fixes for (and that got merged into master - #33, #32, #32, #30, #20, #18). It would be really helpful for our workflows to get a new default
cargo apk
when installing it.The text was updated successfully, but these errors were encountered: