# PR: Fix MiniScheduler::Web integration with Sidekiq 8

**URL:** https://meta.discourse.org/t/pr-fix-minischeduler-web-integration-with-sidekiq-8/400645
**Category:** Development
**Created:** [April 14, 2026, 10:24pm UTC](https://meta.discourse.org/t/pr-fix-minischeduler-web-integration-with-sidekiq-8/400645 "2026-04-14T22:24:55Z")
**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: [April 14, 2026, 10:24pm UTC](https://meta.discourse.org/t/pr-fix-minischeduler-web-integration-with-sidekiq-8/400645/1 "2026-04-14T22:24:55Z")

</div>

In my last PR, I broke the `MiniScheduler::Web` integration by accident:

The current release (v0.19.0) throws errors the moment you call `require “mini_scheduler/web”`. Root cause is a change in the API that `Sidekiq::Web` provides to register extensions. This wasn’t noticed in testing, simply because there were no tests for that module (I assumed there were, but didn’t double check 😅 ).

I have prepared another PR to remedy this: [Fix MiniScheduler::Web integration with Sidekiq 8 by dmke · Pull Request #68 · discourse/mini\_scheduler · GitHub](https://github.com/discourse/mini_scheduler/pull/68)

---

_[View the full topic](https://meta.discourse.org/t/pr-fix-minischeduler-web-integration-with-sidekiq-8/400645)._