- Test release
- Test release again
- Test release
- More convenient namespaces
- Update AWS Core and SQS deps to 3.3.0
- Release 2.0.0
- Add configuration extension that accepts
AWSCredentials
- thanks MooseMagnet
- Update to Rebus 3
- Update to Rebus 4
- Add .NET Core support (netstandard 1.3)
- Change message format to break out of SQS's limitation of being able to transfer only 10 headers - thanks mvandevy
- Fix csproj - thanks robvanpamel
- Add ability to use an external timeout manager or Rebus' ordinary timeout managers to overcome SQS limitations
- Add ability to skip queue creation - thanks robvanpamel
- Remember to configure visibility timeout for queues created by Rebus - thanks micdah
- Additional one-way client configuration overloads - thanks jonathanyong81
- Fix bug that did not limit size of sent message batches to 10
- Do not create queues when configuration says not to - thanks robvanpamel
- Add configurable factory method for customizing which implementation of
IAmazonSQS
is used - thanks dietermijle
- Fixed issue where invalid delay value was being sent to SQS - thanks ajacksms :)
- Change all use of
AmazonSQSClient
to use instance returned from the options passed to the transport, and keep the instance for its entire lifetime - Enable falling back to EC2 roles by leaving out credentials when configuring Rebus
- Allow for using FIFO queues by picking up
MessageGroupId
andMessageDeduplicationId
from Rebus headers and setting them on queue request entries - thanks knepe
- Update to Rebus 6
- Update aqssdk.sqs to 3.3.103 and Rebus to 6.3.1 - thanks jcmdsbr
- Update aqssdk.sqs to 3.3.103.21 - thanks jcmdsbr
- Fix bug that would cause deferred messages to not adhere to Rebus' routing configuration
- Make outgoing message batch size configurable - thanks dietermijle
- Update awssdk.sqs dependency to 3.5.1.20
- Remove dependency on that funny security token nuggie
- Fix bug that would cause inability to manually dead-letter messages
- Pass
CancellationToken.None
to receive call of SQS client, to avoid leaving unacked message on the server when shutting down - thanks xhafan
- Add ability to provide a function that customizes the visibility timeout when message delivery has failed
- Update awssdk.sqs dep to 3.7.1 because that gives a lot of flexibility
- Update to Rebus 8
- Update awssdk.sqs dependency to 3.7.300.2