Release co-ordination: v2.0.2

[xurizaemon]

Hey @davidar - thanks for adding me as a collaborator :)

I've created a draft release of v2.0.2 per docs at managing releases in a repository. I didn't see the "create a discussion" checkbox (perms, probably) so I've manually opened this issue. Assigning you as FYI.

Is v2.0.2 the correct next release? It's a bugfix / patch IMO, but we're changing SDK from 9 to 12. Maybe 2.1.0 is more appropriate, but there are no new features.

I have access sufficient to publish but want to check in with you first :)

[xurizaemon]

I'm going to publish this release, hope that's OK!

[xurizaemon]

Publishing the release doesn't seem to have kicked off the NPM publish action I expected. Guessing that my access to the repo doesn't confer access to the NPM publish token.

We should fix that (might be a manual publish for you @davidar ... sorry!)

We should get v2.0.3 out with #29 included anyway?

[davidar]

Oops, sorry for the lack of response. All looks good to me :)

I'll see what I can do about NPM access when I have a chance

[davidar]

Ah, I remember, I started setting up the CI integration for publishing, but then wasn't particularly happy that the automation tokens grant unlimited access to my NPM account, hopefully npm/roadmap#10 will be resolved soon

In the meantime I've added you as a maintainer on NPM, is that sufficient?

We should get v2.0.3 out with #29 included anyway?

Sounds good