[Chore] Notes for next release

[jlizen]

Noting some non-obvious changes that we will need for our next release, that deviate from standard release-plz handling:

• Make Telemetry API log record type generic #1098 - this requires a minor version bump of lambda-extension - even though cargo-semver-checks is happy, we have a risk of inference breakage if somebody is directly constructing a variant of the LambdaTelemetryRecord enum that doesn't have the new generic. Since, then it won't infer the default of String. Very unlikely to affect anybody, but worth the minor bump + release note mention
• lambda-events also needs a minor version bump due to a new deprecation (though cargo-semver-checks flags that one)

[jlizen]

cc @darklight3it fyi, i think you are planning to run the next release

[jlizen]

Just a side note, along with trusted publishing being broken, looks like integration tests need credentials fixed. Probably another artifact of the github org move? I thought we had fixed it though...

[jlizen]

Some other notable features for next release, by @darklight3it 's request:

• lambda-events builder API to make it more ergonomic to construct #[non_exhaustive] structs, especially if they have no default - Add builder pattern support for event response types #1090
• lambda-extension support for deserializing telemetry records directly as json - Make Telemetry API log record type generic #1098
• multitenancy support - Add tenant-id support #1082
• vpc lattice events (lambda-http support coming up next) - feat(lambda-events): add VPC Lattice event structures #1036
• lambda-events control tower lifecycle event support - feat(lambda-events): add Control Tower lifecycle events module #1107

[jlizen]

Another: #1114 - support for x509 / passwordless custom authorizers in iotcore

[jlizen]

Re: release-plz, probably after fixing permissions, we will hit another bug that needs #1115

[darklight3it]

I think we can close this.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.