v10.0.0-canary.2

Potentially Breaking Changes

SQS Consumer has been transitioned to use ESM in its codebase, in order to support this, we have had to change how we deploy the package in order to build both ESM and CJS versions of the package.

This may cause issues with your software, if it does, please let us know.

What's Changed

• feat!: transitioning to ESM by @nicholasgriffintn in #476

Full Changelog: v9.1.0...v10.0.0-canary.2

v9.1.0

9.1.0 (2024-03-12)

Features

• feat: Add useQueueUrlAsEndpoint to ConsumerOptions by @mogu4iy (#472) (075bd54)

Bug Fixes

• handle CredentialsProviderError from AWS SDK JS v3 by @jamesmbourne (#474) (9a14d66)

Chores

• version bump to 9.1.0 (c031e1e)

v9.0.0

9.0.0 (2024-03-11)

⚠ BREAKING CHANGES

• removed handler_processing debugger in favour of status (consumer.status.isPolling) (#470)
• replaced the isRunning method with status (Please now use consumer.status.isRunning to check this state) (#459)

Potentially Breaking Changes

• We upgraded the AWS SDK to the latest major version. (#468)

Features

• removing handler_processing debugger in favour of status (#470) (b554da6)
• replacing the isRunning method with status (#459) (9f07383)

Chores

• adding a link to the documentation (#471) (bd7fbbb)
• deps: upgrading dependencies - March 24 (#468) (2d342cd)
• handle breaking changes (2924ca2)
• release: v9.0.0 (bc5593c)
• upgrading @semantic-release/npm (bed4dc6)

v8.2.0

8.2.0 (2024-02-06)

Features

• Wait for msgs to be processed before emitting stopped (by @barwin) (#454) (0fa5305)

Chores

• removing semantic git (b834205)
• updating release config (6b95edb)

v8.1.5

8.1.5 (2024-01-21)

Chores

• adding publishConfig for provenance (c64e3ba)

v8.1.4

8.1.4 (2024-01-21)

Chores

• changing CI to set NODE_AUTH_TOKEN instead (534e42c)
• changing release workflow to use semantic versioning (ccf92ee)
• creating workflow for tagging merges (2629729)
• updating attributeNames type docs (#452) (84385d2)

v8.1.3

Changes

• Updated the repository URL to the new format
• Added a CI process for deploying to NPM, with NPM Provenance

Full Changelog: v8.1.0...v8.1.3

v8.1.0

What's Changed

• chore: clarify how acknowledgement works by @nicholasgriffintn in #445
• feat: adding a flag to force consumer to always acknowledge by @nicholasgriffintn in #446

Full Changelog: v8.0.0...v8.1.0

v8.0.0

BREAKING CHANGE

This release is a breaking change as it upgrades the aws-sdk version past the version that changes the communication protocol from XML to JSON, as described here.

Upgrading to this version will require you to ensure that any upstream or downstream dependencies have been configured to support this new protocol.

What's Changed

• chore: upgrade @aws-sdk/client-sqs to version which supports sqs json protocol by @petrisorciprian-vitals in #440

New Contributors

• @petrisorciprian-vitals made their first contribution in #440

Full Changelog: v7.5.0...v8.0.0

v7.5.0

Potentially Breaking

The way errors are handled was changed in the PR #414, it's possible that this may break implementations that expect errors to be produced in a certain way, in our tests, against our own use of sqs-consumer, this release was backwards compatible so based on our assumptions, we have kept this as a minor release, but you might want to check your error handling works as you expect after upgrading.

Features

• feat: support non-standard errors by @aradbar in #414
• Add pollingWaitTimeMs to UpdatableOptions by @maximpoleley in #436

CI Changes

• chore: updating workflow deps by @nicholasgriffintn in #437
• fix: updating pages deploy version by @nicholasgriffintn in #438

New Contributors

• @maximpoleley made their first contribution in #436

Full Changelog: v7.4.0...v7.5.0