NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #1060 most downloaded on Packagist
PHP client for beanstalkd queue
Latest stable
v8.0.2
Last release 1 years ago
11 Nov 2025
Release timing varies
gaps range from 8 days to 6 months
Most releases are documented
notes for 29 of 39 stable releases
Nothing withdrawn
no release was ever pulled
14 years old
48 releases · first in 2013
Drag across the ruler to compare, or tap a release to open it.
Values/JobStats: cast int fields to handle Beanstalkd float values + CI cleanups
Dead TCP connections handling in SocketSocket causes 100% CPU usage. (e63cce9), closes pheanstalk/pheanstalk#305
Your coding agent can read these notes before it upgrades. Set up the MCP server →
fix!: Dead TCP connections handling (93250e9), closes pheanstalk/pheanstalk#303
improve error message on connection creation
# 7.1.0 (2025-07-23) ### Features * add constructor
Don't throw an exception when a signal is dispatched
add $tube to TubeNotFoundException
add disconnect() method to release resources deterministically
automatically reconnect upon socket error
ensure socket is not left in a half-read/written state on error
chore!: drop support for php 8.1 and 8.2
drops php 8.1 and php.2
chore(ci): update php versions in automated release script
chore: empty commit to trigger ci
chore: fix psalm in ci
chore(ci): don't run psalm on php8.4
fix(ci): remove psalm
drops php 8.1 and php.2
add close() method to release resources deterministically
automatically reconnect upon socket error
ensure socket is not left in a half-read/written state on error
give info about socket_create error
Add missing fields to ServerStats
remove @internal from exception base classes
## 5.0.6 (2024-09-05) ### Bug Fixes * explicit nullable declarations
## 5.0.5 (2024-03-04) ### Bug Fixes * accept empty data
Change the response parsing to treat 0 as a number
add readme snippets to checks for static analysis
Uncaught Error: Cannot unset readonly property Pheanstalk\Socket\SocketSocket::$socket in SocketSocket.php on line 138
## 5.0.1 (2023-09-11) ### Bug Fixes * automated releases (f1a4355) * do stable release
Nothing published for this version
ci: switch to rc for semantic-release
Nothing published for this version
Nothing published for this version
Second alpha release. Documentation still needs significant work, but this code should be working. Test coverage is very high and we have both unit te
Second alpha release. Documentation still needs significant work, but this code should be working. Test coverage is very high and we have both unit tests as well as integration tests.
Full Changelog: https://github.com/pheanstalk/pheanstalk/compare/v5.0.0-alpha1...v5.0.0-alpha2
Alpha release of V5, this is an almost complete rewrite so changes in your necessary.
Alpha release of V5, this is an almost complete rewrite so changes in your necessary.
On reconnection dispatch the ignore command by @gdsmith in https://github.com/pheanstalk/pheanstalk/pull/259
Full Changelog: https://github.com/pheanstalk/pheanstalk/compare/v4.0.4...v4.0.5
Nothing published for this version
Nothing published for this version
Nothing published for this version
This release contains the fix for #205, it was found and fixed by @panicoschr.
This release contains the fix for #205, it was found and fixed by @panicoschr.
Version 4 of Pheanstalk is a partial rework of the most popular PHP library for Beanstalkd.
Version 4 of Pheanstalk is a partial rework of the most popular PHP library for Beanstalkd.
This release removes support for persistent connections and removes functions with side effects like putInTube.
To be more flexible in deployment Pheanstalk now supports different socket implementations, if possible it will default to using the sockets extension. Advantage of this extension is that it allows us to enable tcp KEEP ALIVE.
In Pheanstalk one common issue that people ran into was an undetectable connection failure. The consumer would wait infinitely but no new jobs would come in. For a lot of reasons it can be impossible for PHP (or even the underlying OS) to detect that a connection was dropped. For this reason we recommend always:
Please test your code thoroughly before deploying version 4 in production. Specifically make sure your code handles exceptions and takes appropriate actions.
Nothing published for this version
Nothing published for this version
Nothing published for this version
This release fixes a bug that could, in certain cases, cause data to be lost from a connection. Due to the way beanstalk reservations work no data is
This release fixes a bug that could, in certain cases, cause data to be lost from a connection. Due to the way beanstalk reservations work no data is permanently lost and the main effect of this would be a delay in task execution.
Thanks for pointing out the problem @mialex!
One issue that was fixed in this release was the risk of an infinite loop in Connection::getLine(). Now after a timeout, configurable via ini-set('def
This is a maintenance release.
One issue that was fixed in this release was the risk of an infinite loop in Connection::getLine().
Now after a timeout, configurable via ini-set('default_socket_timeout', $timeout), the getLine() function will throw an exception to bring it in line with Connection::read() and Connection::write().
If your worker has to potentially wait a long time for jobs you might start to see exceptions that you did not see before. Even though this behavior is a change it allows you to actually detect errors instead of just waiting forever.
If your worker is currently managed by a supervisor (ie, it restarts after it dies), set your socket timeout to a value like 3600. This means that if the worker doesn't get jobs for 12 hours, it will be restarted 12 times, but in return, if the connection is dead the worker will restart after at most 1 hour and resume working.
If a crash of your worker results in manually having to restart it you should really change the configuration.
One option that partially resolves this is properly catching errors in reserve(), socket errors are in that sense nothing new, the changes in this version just make them more consistent in certain cases.
`$pheanstalk->resumeTube()` method, thanks @YanivD.
$pheanstalk->resumeTube() method, thanks @YanivD.$pheanstalk->getConnection()->disconnect() method, thanks @julman99 and @Xophe.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.