Version v0.14.0 released with breaking change.

[adrianosela]

Notes:

Not sure of a better way to communicate this than a github issue. You may want to be aware that v0.14.0 (minor update) was released with a breaking change - introduced in:

• ref: Use a Context type mapping to map[string]interface{} #444

Folks already defining the Contexts field of the Event object as a map[string]interface{} will get build-time errors:

cannot use make(map[string]interface{}) (value of type map[string]interface{}) as type map[string]map[string]interface{} in struct literal

[kamilogorek]

Hey, thanks for filling out the issue. As we are still in pre-v1 release, we are still ironing out the API and concrete types for the SDK.
As per SemVer, we are allowed to do that without bumping a major release - https://semver.org/#spec-item-4
We already did that multiple times in the past, however this time, I completely forgot about this change, as it's been 5mo since I merged it 😅

The change is legitimate, as context payload for the event can only accept nested map, where key has to be a string.
So in theory map[string]interface{} can cover that, but it's also too generic, as map[string]map[string]interface{} is the only allowed type by our processing servers.

Updated changelog and release notes to include that information: #480

Cheers!