glide-mq 0.20 lists your job schedulers with a hard size limit
2 hours ago
glide-mq 0.20 adds one new call to the Queue. getRepeatableJobsBounded lists every job scheduler on a queue, the schedules that add a job on a cron pattern or an interval, but only when their count fits under a limit you pass in. The rest of the release fixes links in the agent skills and patches development dependencies.
Ask about this presentation
Chapters
Show transcriptHide transcript
glide-mq 0.20 adds one new call to the Queue. getRepeatableJobsBounded lists every job scheduler on a queue, the schedules that add a job on a cron pattern or an interval, but only when their count fits under a limit you pass in. The rest of the release fixes links in the agent skills and patches development dependencies.
Here is a queue with five schedulers, and a limit of four. The existing getRepeatableJobs call hands back the whole inventory, whatever its size. The bounded call counts first. Five is more than four, so it throws a range error that names both numbers, and you get no entries at all. Any list it does return is complete.
A scheduler can be added at any moment, even while you are listing them. So the size check and the read run inside a single Valkey function call. Nothing can land between them and push the result past your limit. This ships as version 136 of the server function library, and the queue loads it onto the server when it connects.
Every entry is also checked as it comes back. The existing call quietly skips a value that isn't valid JSON. The bounded call throws instead and names the scheduler, and it does the same for a missing or out-of-range field, like the next run time. It also reads the stored job templates without running your queue's custom serializer.
The limit has to be a positive whole number. Zero, a fraction, or not-a-number throws a range error before the queue even talks to the server. The in-memory TestQueue, from glide-mq/testing, gets the same method with the same size check, so your unit tests can cover the over-limit path too.
glide-mq ships agent skills, the guides a coding agent reads when it works with the library. Each skill installs on its own, without the repository's docs folder. So their references into that folder led nowhere. They now point at the docs on GitHub. A new lint step fails when a skill links outside its own folder, or to a file that doesn't exist.
The security work is in the development and example dependencies. Vitest, body-parser, undici and Zod move to patched versions, Vite goes from 8.3.1 to 8.3.5, and what your app installs at runtime is unchanged. CI and the npm publish job now audit development dependencies too, down to low severity findings. Before this, CI checked only runtime dependencies, at moderate and above.
To upgrade, install glide-mq version 0.20.0 from npm. getRepeatableJobs is unchanged, and so are the runtime dependencies. The one thing to plan for is that the bounded call returns all or nothing. Set the limit above the number of schedulers you expect to keep. That's glide-mq 0.20, a scheduler listing with a hard size limit.