[GH-ISSUE #735] [Discussion/Proposal] Seeking Updates on asynq Roadmap #359

New issue

Open

opened 2026-03-02 05:20:41 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 05:20:41 +03:00

Owner

Originally created by @ryan961 on GitHub (Sep 7, 2023).
Original GitHub issue: https://github.com/hibiken/asynq/issues/735

Originally assigned to: @hibiken on GitHub.

Hello @hibiken ,

Thank you for contributing this great tool library. I'm one of the many users and beneficiaries of asynq, having used it stably in my projects for two years. However, in recent months I've noticed development seems to have stalled somewhat, including dependency upgrades (Go version upgrades, etc), discussions in the issues, and processing of pull requests. This is making asynq gradually become an impediment to project version iteration (especially after releases like Go v1.19, v1.21...), to the point where I have to carefully consider whether to continue using asynq in new projects. I'm wondering what are your thoughts and timeline regarding future iterations and upgrades of the library (Go version upgrades, logger module upgrades , etc.)?

I know it takes great effort and challenges to continuously maintain such an excellent distributed task queue library. If you need help and can provide specific requests, I'm also happy to contribute code.

Looking forward to your reply. 😊

Originally created by @ryan961 on GitHub (Sep 7, 2023). Original GitHub issue: https://github.com/hibiken/asynq/issues/735 Originally assigned to: @hibiken on GitHub. Hello @hibiken , Thank you for contributing this great tool library. I'm one of the many users and beneficiaries of asynq, having used it stably in my projects for two years. However, in recent months I've noticed development seems to have stalled somewhat, including dependency upgrades (Go version upgrades, etc), discussions in the issues, and processing of pull requests. This is making asynq gradually become an impediment to project version iteration (especially after releases like Go v1.19, v1.21...), to the point where I have to carefully consider whether to continue using asynq in new projects. I'm wondering what are your thoughts and timeline regarding future iterations and upgrades of the library (Go version upgrades, [logger module upgrades](https://github.com/hibiken/asynq/issues/670) , etc.)? I know it takes great effort and challenges to continuously maintain such an excellent distributed task queue library. If you need help and can provide specific requests, I'm also happy to contribute code. Looking forward to your reply. 😊

kerem added the

enhancement

label

2026-03-02 05:20:41 +03:00

kerem commented

2026-03-02 05:20:42 +03:00

Author

Owner

@kamikazechaser commented on GitHub (Sep 7, 2023):

Some dependencies have been upgraded (Yet to be released). Right now the plan is to immediately support 1.19 and 1.20 (see #719). The CI test suite needs to be updated for that.

Support for 1.21 might taker longer with the way the toolchain now works (it would force anyone who imported asynq to update to 1.21).

Features and refactoring might take longer than expected though.

@kamikazechaser commented on GitHub (Sep 7, 2023): Some dependencies have been upgraded (Yet to be released). Right now the plan is to immediately support 1.19 and 1.20 (see #719). The CI test suite needs to be updated for that. Support for 1.21 might taker longer with the way the toolchain now works (it would force anyone who imported asynq to update to 1.21). Features and refactoring might take longer than expected though.

kerem commented

2026-03-02 05:20:42 +03:00

Author

Owner

@hibiken commented on GitHub (Sep 8, 2023):

Hi @ryan961,
Thanks for opening this issue and asking those questions.
As for Go version support, we have a proposal (thanks to @kamikazechaser) to support latest 2 go versions #719.
We also have a bot for dependency upgrades (but we need to do a better job of approving/merging PRs there).

As for the roadmap, I don't have a clear plan just yet. If you could put together one I'd appreciate that! If you are interested in contributing to the project, please feel free to open or comment on issues/prs. I will add you as a collaborator after that!

@hibiken commented on GitHub (Sep 8, 2023): Hi @ryan961, Thanks for opening this issue and asking those questions. As for Go version support, we have a proposal (thanks to @kamikazechaser) to support latest 2 go versions #719. We also have a bot for dependency upgrades (but we need to do a better job of approving/merging PRs there). As for the roadmap, I don't have a clear plan just yet. If you could put together one I'd appreciate that! If you are interested in contributing to the project, please feel free to open or comment on issues/prs. I will add you as a collaborator after that!

kerem referenced this issue

2026-03-02 06:05:22 +03:00

[PR #375] [MERGED] feat: allow configuration of intervals #728

kerem referenced this issue

2026-03-07 22:06:49 +03:00

[GH-ISSUE #359] [FEATURE REQUEST] forwarder.interval support dynamic adjustment #1174

kerem referenced this issue

2026-03-07 22:12:59 +03:00

[PR #375] [MERGED] feat: allow configuration of intervals #1740

kerem referenced this issue

2026-03-15 19:35:19 +03:00

[GH-ISSUE #359] [FEATURE REQUEST] forwarder.interval support dynamic adjustment #2184