Skip to content

Conversation

@lackstein
Copy link
Member

  • We now use Faktory v1.9.3
  • Docker image now uses Alpine 3.21
  • All actions used in CI have been updated
  • Goreleaser configuration has been updated to support v2

@lackstein lackstein requested a review from jagonalez December 8, 2025 17:41
Copy link
Collaborator

@jagonalez jagonalez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Two things I noticed in the 1.9.0 changelog:

Faktory now refuses further connections on :7419 if the connection count is larger than allowed, 2000 in Faktory or your licensed amount in Faktory Enterprise. [#476]
The INFO response has changed slightly, all elements now have well-defined types [#474] Deprecate client.Info Go API, add new client.CurrentState Go API which is almost identical to client.Info but has a strongly-typed response.

I don't think we'll run into an issues with the 2k connection limit

the core internal page relies on the info response - so that might break depending on what changed.

@lackstein
Copy link
Member Author

the core internal page relies on the info response - so that might break depending on what changed.

Good to know. I'll make sure to update that before we deploy this.

@lackstein lackstein merged commit 625b4db into main Dec 8, 2025
2 checks passed
@lackstein lackstein deleted the nl/faktory-1.9.3 branch December 8, 2025 18:47
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.

2 participants