You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the SDK requirements documentation, it says "Each SDK supports the latest(N), and N-1, major releases of the CloudEvent spec", with a special case being 1.0 as latest with 0.3 recommended support.
Ultimately, dropping support for 0.2 should make maintenance simpler. From npm download numbers, I guess it's hard to tease out how many are still on 0.2, but this seems reasonable.
I wonder also what the versioning strategy is. Is the npm module is versioned independently from the spec version? It seems like it must be - at least for minor and patch levels.
Activity
grant commentedon Apr 25, 2020
I agree in dropping 0.2 (and I support dropping 0.3).
helio-frota commentedon Apr 27, 2020
+1 in dropping support for 0.2
lance commentedon Apr 27, 2020
@grant currently it is recommended that adapters continue to support v0.3. See: https://github.com/cloudevents/spec/blob/master/SDK.md#contribution-acceptance
grant commentedon Apr 27, 2020
I propose we follow the versioning of the most mature CE SDK, Go, and support v1 and v2.
https://github.com/cloudevents/sdk-go
However, this library needs a bit of work before then.
fabiojose commentedon Apr 27, 2020
+1
src,fix: drop support for v0.2 and clean up contenttype
src,fix: drop support for v0.2 and clean up contenttype
src,fix: drop support for v0.2 and clean up contenttype