Skip to content

Rename Quartz.Redis package to Quartz.Extensions.Redis#3053

Merged
lahma merged 2 commits into
3.xfrom
rename-redis-package-3x
Apr 25, 2026
Merged

Rename Quartz.Redis package to Quartz.Extensions.Redis#3053
lahma merged 2 commits into
3.xfrom
rename-redis-package-3x

Conversation

@lahma

@lahma lahma commented Apr 25, 2026

Copy link
Copy Markdown
Member

Summary

  • The package id Quartz.Redis is already taken on nuget.org by an unrelated v1.0.0 (published before our Quartz.* prefix reservation existed), so the 3.x release pipeline gets HTTP 403 when trying to publish under that id. Commit cc2a646 worked around it by setting IsPackable=false; this PR picks an available id and removes the workaround.
  • New id: Quartz.Extensions.Redis — chosen as an umbrella id (mirroring Quartz.Extensions.DependencyInjection / Quartz.Extensions.Hosting) so that future Redis capabilities — e.g. an actual Redis-backed job store — can ship in the same package rather than fragmenting across multiple ids.
  • Also moves RedisSemaphore from Quartz.Impl.AdoJobStore to Quartz.Impl.Redis. The class implements ISemaphore and doesn't depend on ADO-specific types like JobStoreSupport — only on lock abstractions (ISemaphore, ITablePrefixAware, ConnectionAndTransactionHolder) that happen to live in the AdoJobStore namespace today, so the file still has a using Quartz.Impl.AdoJobStore;. Integration test fixtures move along with it.
  • The package was never published, so there are no consumers to migrate — no compat shims, no type forwarders.

Rebased onto 3.x after #3054 merged so CI restore is no longer blocked by the OpenTelemetry NU1902.

Test plan

  • dotnet build Quartz.slnx -c Release — full solution clean, 0 warnings / 0 errors (after rebase on the merged vuln fix)
  • dotnet build src/Quartz.Extensions.Redis/Quartz.Extensions.Redis.csproj -c Release — clean across net462, netstandard2.0, net8.0
  • dotnet build src/Quartz.Tests.Integration/Quartz.Tests.Integration.csproj -c Release — clean
  • dotnet build src/Quartz.Tests.Unit/Quartz.Tests.Unit.csproj -c Release — clean
  • dotnet pack src/Quartz.Extensions.Redis/Quartz.Extensions.Redis.csproj — produces Quartz.Extensions.Redis.<version>.nupkg with the new id, assembly Quartz.Extensions.Redis.dll for all 3 TFMs, and redis.md embedded as the package readme
  • CI integration test job (pr-integration-redis.yml) passes — confirms the renamed project + relocated test fixtures still wire up against a real Redis container

Pre-publish prerequisite

Before tagging the next 3.x release, please confirm in the NuGet portal that the existing Quartz.* prefix reservation covers Quartz.Extensions.* (it should, but the cc2a646 incident was caused by an unverified assumption about prefix coverage).

A follow-up PR will port the same change to main (4.x).

🤖 Generated with Claude Code

lahma and others added 2 commits April 25, 2026 13:38
The package id Quartz.Redis is already taken on nuget.org by an unrelated
v1.0.0 published before our prefix reservation existed, so the 3.x release
pipeline gets HTTP 403 when trying to publish under that id. Commit
cc2a646 worked around it by setting IsPackable=false; this change picks
a new, available id and removes the workaround.

Quartz.Extensions.Redis was chosen as an umbrella id (mirroring
Quartz.Extensions.DependencyInjection / Quartz.Extensions.Hosting) so that
future Redis capabilities — e.g. an actual Redis-backed job store — can
ship in the same package rather than fragmenting across multiple ids.

Also moves RedisSemaphore from Quartz.Impl.AdoJobStore to Quartz.Impl.Redis;
the class implements ISemaphore and has no dependency on the ADO job store,
so its old namespace was misleading. Integration test fixtures move along
with it. The package was never published, so there are no consumers to
migrate.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Cosmetic only: places Quartz.Extensions.Redis next to
Quartz.Extensions.DependencyInjection so the Quartz.Extensions.* family
sits contiguously. No behavioral change.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
@lahma
lahma force-pushed the rename-redis-package-3x branch from 775abb8 to 22aa280 Compare April 25, 2026 10:38
@sonarqubecloud

Copy link
Copy Markdown

@lahma
lahma merged commit 1754458 into 3.x Apr 25, 2026
16 checks passed
@lahma
lahma deleted the rename-redis-package-3x branch April 25, 2026 10:42
lahma added a commit that referenced this pull request Apr 25, 2026
Port of #3053 (3.x) to 4.x. The package id Quartz.Redis is already taken
on nuget.org by an unrelated v1.0.0 published before our prefix
reservation existed, so any attempt to publish the package fails with
HTTP 403.

Quartz.Extensions.Redis was chosen as an umbrella id (mirroring
Quartz.Extensions.DependencyInjection / Quartz.Extensions.Hosting) so
that future Redis capabilities — e.g. an actual Redis-backed job store —
can ship in the same package rather than fragmenting across multiple ids.

Also moves RedisSemaphore from Quartz.Impl.AdoJobStore to
Quartz.Impl.Redis. The class implements ISemaphore and doesn't depend on
ADO-specific types like JobStoreSupport — only on lock abstractions
(ISemaphore, ITablePrefixAware, ConnectionAndTransactionHolder) that
happen to live in the AdoJobStore namespace today, so the file still has
a using Quartz.Impl.AdoJobStore;. Integration test fixtures move along
with it.

Both quartz-3.x/packages/redis.md and quartz-4.x/packages/redis.md are
updated since main carries both copies of the docs.

The package was never published, so there are no consumers to migrate —
no compat shims, no type forwarders.

Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
This was referenced Apr 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant