Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

Releases: Webador/SlmQueueSqs

v0.4.0

13 Oct 16:20
0.4.0
Compare
Choose a tag to compare
  • First stable release in 0.4.x branch

v0.4.0-beta3

09 Oct 12:08
0.4.0-beta3
Compare
Choose a tag to compare
v0.4.0-beta3 Pre-release
Pre-release
  • [BC] Due to changes in SlmQueue (changelog) existing jobs won't be able to be executed correctly.

v0.4.0-beta2

07 Oct 09:11
0.4.0-beta2
Compare
Choose a tag to compare
v0.4.0-beta2 Pre-release
Pre-release
  • Update dependency to SlmQueue 0.4.0-beta2

v0.4.0-beta1

02 Oct 17:55
0.4.0-beta1
Compare
Choose a tag to compare
v0.4.0-beta1 Pre-release
Pre-release
  • [BC] Bump SlmQueue dependency to 0.4. Please read SlmQueue CHANGELOG for further information
  • batchDelete now also automatically splice jobs if you submit more than 10 jobs.

v0.3.1

19 May 09:09
0.3.1
Compare
Choose a tag to compare
  • Custom metadata set to a job is now correctly retrieved when jobs are pushed, along SQS own metadata.

v0.3.0

30 Mar 17:08
0.3.0
Compare
Choose a tag to compare
  • First release for 0.3 branch

v0.3.0-beta3

02 Mar 17:13
0.3.0-beta3
Compare
Choose a tag to compare
v0.3.0-beta3 Pre-release
Pre-release
  • Update to 0.3-beta 3 of SlmQueue

v0.3.0-beta2

22 Feb 23:13
0.3.0-beta2
Compare
Choose a tag to compare
v0.3.0-beta2 Pre-release
Pre-release
  • Update dependency to SlmQueue beta-2
  • Worker factory has been moved to SlmQueue

v0.3.0-beta1

09 Jan 15:26
0.3.0-beta1
Compare
Choose a tag to compare
v0.3.0-beta1 Pre-release
Pre-release
  • Use AWS ZF 2 module
  • pop method now only returns 1 job. You must use batchPop to return more than one job.
  • You can now directly specify a queue URL for a given queue name (hence avoiding one HTTP request)
  • [BC] SQS service has been removed, please now use the official AWS SDK to list or create queues
  • [BC] SqsQueue now uses getQueueUrl instead of createQueue. This means that you must first create queues using the official SQS client or the AWS console. This change has been made to offer a more predictable behaviour for SQS queues.