release: v0.13.0#213
Merged
Merged
Conversation
Lockstep release of all packages 0.12.0 → 0.13.0 (minor): adds the @qified/valkey provider and makes Redis/Valkey task claims atomic with per-delivery fencing tokens, plus a tooling refresh. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014cLAa8HaTokNu5wBM7cM6x
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #213 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 12 12
Lines 1659 1659
Branches 287 288 +1
=========================================
Hits 1659 1659 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
There was a problem hiding this comment.
Code Review
This pull request bumps the version of the monorepo and its packages, including @qified/mono, @qified/nats, qified, @qified/rabbitmq, @qified/redis, @qified/valkey, and @qified/zeromq, from 0.12.0 to 0.13.0. There are no review comments, and I have no feedback to provide.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release summary
Lockstep release of all packages
0.12.0 → 0.13.0(minor): the new@qified/valkeyprovider plus atomic, fencing-token task-claim safety for@qified/redisand@qified/valkey, on top of a dependency/tooling refresh.Packages
@qified/valkey0.12.00.13.0@qified/redis0.12.00.13.0redis6.0→6.1qified0.12.00.13.0hookified3.0.1@qified/nats0.12.00.13.0hookified3.0.1@qified/rabbitmq0.12.00.13.0hookified3.0.1@qified/zeromq0.12.00.13.0@qified/mono(root)0.12.00.13.0v0.13.0 — 2026-07-16
Adds the @qified/valkey provider and makes Redis/Valkey task claims atomic with fencing tokens.
Features
add the
@qified/valkeyprovider — Valkey pub/sub + a reliable task queue on theiovalkeyclient, mirroring@qified/redis(5ceaed2, feat(valkey): add @qified/valkey provider #205)atomic task claim with per-delivery fencing tokens for
@qified/redisand@qified/valkey— claim/ack/reject/extend/timeout-recovery are now single Lua scripts, so a worker that lost ownership becomes a no-op and a crash can't strand a task or corrupt a newer delivery. Delivery is at-least-once; handlers should be idempotent (47d3087, feat(valkey): add @qified/valkey provider #205)Bug Fixes
SUBSCRIBEfails, prevent a throwing handler from raising an unhandled rejection, andunref()per-task timers (0a594fa, feat(valkey): add @qified/valkey provider #205)Internal
redis6.0.0→6.1.0in@qified/redis(d73e014, @qified/redis - chore: upgrade redis #210)hookified3.0.0→3.0.1across all providers (b460fee, mono - chore: upgrade hookified #209).nvmrcto Node24.18.0and align@types/nodeto^24.13.3(c89aefb, mono - chore: pin .nvmrc to Node 24 and align @types/node #212)engines.nodefloor to^22.19.0to match the docula→undici toolchain (15761a8, mono - chore: raise root engines.node floor to 22.19 #211)docula2.0.0→2.2.0(6806ab5, mono - chore: upgrade docula #208)tsx→4.23.0andtsdown→0.22.4(89e0fec, mono - chore: upgrade TypeScript build tooling #207)@biomejs/biome→2.5.3,vitest+@vitest/coverage-v8→4.1.10(661fc4f, mono - chore: upgrade code quality dependencies #206)Contributors
Full List of Changes
Full diff: v0.12.0...v0.13.0
Verification
pnpm install --frozen-lockfilesucceeds — no lockfile change (workspace cross-deps useworkspace:^)pnpm buildsucceeds — all packages compilepnpm testpasses locally — qified 132, nats 80, rabbitmq 114, redis 88, valkey 88, zeromq 8; 100% coverage (provider suites run against live Docker services)CHANGELOG.mdis kept in this repo — notes live here and in the GitHub Release)Post-merge
v0.13.0with the notes above — therelease.yamlworkflow (release: [released]) runspnpm publish:packages, publishing all 6 packages to npm via OIDC trusted publishing with provenance.@qified/valkey: it was added in feat(valkey): add @qified/valkey provider #205, after the OIDC setup (ci: migrate npm release to OIDC trusted publishing with provenance #203/release: v0.12.0 #204) that covered the original 5 packages. Before releasing, add its npm Trusted Publisher (orgjaredwray, repoqified, workflowrelease.yaml) — otherwise the OIDC publish will fail auth for that one package. The other 5 are already configured.🤖 Generated with Claude Code
Generated by Claude Code