You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be helpful to setup a Github Action release workflow that also published the crate to crates.io? Could be exclusively run if the commit message contains release for example.
edit: mostly considering semantic release actions for Rust aren't quite there yet from what I've been able to find.
Is there a timeline for a new release to catch #64?
Sorry for the delay, I'll try to get the next release out in next 2 weeks, as there are some bugs that I want to fix first.
Would it be helpful to setup a Github Action release workflow that also published the crate to crates.io? Could be exclusively run if the commit message contains release for example.
edit: mostly considering semantic release actions for Rust aren't quite there yet from what I've been able to find.
Tagged releases are pushed via cargo publish from a clean checkout. While I'm not against using GitHub Actions, I'm not sure I understand what problem are you're trying to solve.
Are there specific issues for each of these bugs the community can help solve?
Tagged releases are pushed via cargo publish from a clean checkout. While I'm not against using GitHub Actions, I'm not sure I understand what problem are you're trying to solve.
True, not specifically a tech problem. Simply a suggestion to make for easy process.
@PiotrSikora when you have the chance would be cool to get this pushed out. Looking to experiment with the new changes to ABI and how this affects our filters. Appreciate your work here.
Activity
Swaagie commentedon Jan 24, 2022
Would it be helpful to setup a Github Action release workflow that also published the crate to crates.io? Could be exclusively run if the commit message contains
release
for example.edit: mostly considering semantic release actions for Rust aren't quite there yet from what I've been able to find.
PiotrSikora commentedon Jan 24, 2022
Sorry for the delay, I'll try to get the next release out in next 2 weeks, as there are some bugs that I want to fix first.
Tagged releases are pushed via
cargo publish
from a clean checkout. While I'm not against using GitHub Actions, I'm not sure I understand what problem are you're trying to solve.Swaagie commentedon Jan 25, 2022
Are there specific issues for each of these bugs the community can help solve?
True, not specifically a tech problem. Simply a suggestion to make for easy process.
PiotrSikora commentedon Feb 11, 2022
Sorry, this will slip into the next week.
cortex93 commentedon Mar 19, 2022
Any progress for this release ?
jcrugzz commentedon Mar 30, 2022
@PiotrSikora when you have the chance would be cool to get this pushed out. Looking to experiment with the new changes to ABI and how this affects our filters. Appreciate your work here.
PiotrSikora commentedon Apr 5, 2022
I've added all the remaining PRs and issues to the v0.2.0 milestone, and the release should be published later this week.
PiotrSikora commentedon Apr 7, 2022
All key PRs are merged, so this is ready to go. I'll make a release on Friday, in case anybody wants to tests it before then.