Publish v3.3.0 which fixes broken data_sync_excluded_exceptions
behaviour
#211
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
3.3.0 reverts changes introduced in 3.1.0 and 3.1.1. In 3.1.0/3.1.1 we merged the
should_capture
method into thebefore_send
method in preparation for swapping outsentry-raven
forsentry-ruby
. However, it broke the "ignore certain errors when they happen during the data sync" behaviour.This is subsequently fixed in v4, but not all apps can/will be upgraded to v4, so we should offer a stable v3.
I've manually published v3.3.0 from the command line, and then merged
main
into this branch as the last commit, to retain the history.Trello: https://trello.com/c/lVDo5gTD/2603-remove-beforesend-shouldcapture-changes-in-govukappconfig-v330