release-plz VS websurfx

My problem with maintaining a changelog during development is it can serve as a source of merge conflicts. Instead, I follow Covnentional Commit style and manually write my changelog entries based on the commits. I have a tool [0] that can show me the relevant commits for a package in my repo and automates the entire release process, including doing sanity checks.

I also feel like releasing from CI is hard, especially if you have multiple packages in a repo [1], including

- You can't as easily introspect the process

- You can't as easily recover from failure

- Getting a lot of the nuance right, like handling releases concurrent to merging of PRs, is difficult

- When the workflow is an ever-present "release PR" that you merge when ready has issues with selecting which packages to release and at what version

I have been considering making a tool to generate changelogs from fragments. Been keeping notes at https://github.com/epage/epage.github.io/issues/23

[0]: https://github.com/crate-ci/cargo-release

[1]: https://github.com/MarcoIeni/release-plz/discussions/1019

Hi 👋 I maintain release-plz, a project enabling maintainers to release Rust packages automatically.

How does this tool differ from release-plz?: https://github.com/marcoIeni/release-plz

Nice, very simple. I like it! You might also want to check out my project: https://github.com/MarcoIeni/release-plz

GitHub release: https://github.com/neon-mmd/websurfx/releases/tag/v1.0.0

Sorry for being late to reach you out. Thanks for trying out Websurfx, but I can help you out in setting up Websurfx. Just a raise an issue here, or you can ask for help here at our discord, we would be glad in helping you out :).

Recently we decided to do error-handling and provide custom error-messages for the errors related to each engine code present under src/engines folder in one of my project websurfx when using error-stack and we wanted to use enums for it and we found that the error-stack project provides no guide, tutorial or example but thanks to one of our maintainers @xffxff, @xffxff provided a really cool solution to this problem and which helped me learn a lot so I decided to share with you all on what I learned from it in this post and how you can wrap errors with enums when using error-stack so stick till the end of the post.

Also, you can check out the docs for steps on how to do docker deployment. I have covered it over there in great depth.

git clone https://github.com/neon-mmd/websurfx.git

Before you look into the code, I would like to explain in brief what the code below does. The code below a function which builds a new random user-agent from the provided browsers and returns it as a string but it is too slow it takes 10 seconds to build and even with caching option enabled it takes around 5-7 seconds but I want to reduce the time it takes by as much as possible. Please provide me with some suggestions or code on how to improve this down in the comments or here in this issue I have opened in my project.

If you'd like to join the WebSurfx team and help shape the future of a privacy-centric search engine, please check out our project on GitHub: WebSurfx GitHub. Feel free to explore the code, open issues, or submit pull requests. Don't hesitate to introduce yourself and share your ideas!