# PR: mini\_scheduler에 Sidekiq 8 지원 추가

**URL:** https://meta.discourse.org/t/pr-add-sidekiq-8-support-to-mini-scheduler/399560
**Category:** Development
**Created:** [3월 30, 2026, 12:06오후 UTC](https://meta.discourse.org/t/pr-add-sidekiq-8-support-to-mini-scheduler/399560 "2026-03-30T12:06:41Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![dmke](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dmke/32/264041_2.png) [@dmke](https://meta.discourse.org/u/dmke)
#### Post date: [3월 30, 2026, 12:06오후 UTC](https://meta.discourse.org/t/pr-add-sidekiq-8-support-to-mini-scheduler/399560/1 "2026-03-30T12:06:42Z")

</div>

누군가 discourse/mini\_scheduler의 이슈 트래커를 보고 있는지 확실하지는 않지만, 방금 PR을 만들었습니다:

> <https://github.com/discourse/mini_scheduler/pull/65>
>
> This:
> 
> \- adds support for Sidekiq 8.0, 8.1
> \- adds Ruby 3.4, 4.0 to CI pipelin…e
> \- adds DragonflyDB to test matrix
> \- updates minimum Ruby version to 3.2
> 
> The MRI version bump is due to a version constraint in Sidekiq \>= 8.0 (https://github.com/sidekiq/sidekiq/commit/13146d5756415b4b5135058b6f960ed11c51a0b2). It would be possible to only require Ruby 3.2+ for Sidekiq 8+, but that (a) requires additional version check code at startup, and (b) a more complicated CI workflow.
> 
> The \`mini\_scheduler\` doesn't seem to need modifications.

(내 Rails 앱 중 하나를 Sidekiq 8.1로 업그레이드하고 있는데, mini\_scheduler가 업데이트해야 할 마지막 의존성입니다 :))

---

_[View the full topic](https://meta.discourse.org/t/pr-add-sidekiq-8-support-to-mini-scheduler/399560)._