considering a new maintenance model for eggbug-rs where if i don’t immediately see that you’ve added malware to the library i’ll just merge it and cut a new breaking release
i like having the library but i don’t like maintaining it lol lmao

translating things, building chill software for my friends, playing ttrpgs, making procedural vector art, learning piano, writing unhinged Utena fanfics, and just vibing
considering a new maintenance model for eggbug-rs where if i don’t immediately see that you’ve added malware to the library i’ll just merge it and cut a new breaking release
i like having the library but i don’t like maintaining it lol lmao
i've written a nice release workflow for nix-your-shell, which has people tag PRs with patch, minor, or major (defaulting to patch), and then merging a PR with one of those tags opens a new PR with the corresponding version bump. then, merging a version bump PR causes a release to be tagged, created as a github release (with a rudimentary changelog generated from the PRs merged), and uploaded to crates.io. it's worked really well and it's very hands-off, so feel free to crib it for your own project :)