João Carvalho

Isn't this behavior usually achieved using Key IDs? (`kid` field on the JWT header)

We at FenixEdu are using Pebble for our theming engine for our FenixEdu application family. [Source here - bennu-portal subproject](https://github.com/FenixEdu/bennu). We are also using it as the main engine for...

We are also using Pebble to implement our own version of Spring's [Initializr](https://github.com/spring-io/initializr), also known as [start.spring.io](https://start.spring.io). The tool generates a Maven project based on some user input, allowing the...

This came from the Contribfest, yes, but haven't yet had the chance to look at the CI errors, will look into it during the weekend.

@dyladan The fix was actually quite simple (updated initially to TS 5.2, but then TS 5.3 came out and my cached `typedoc` dependency didn't bump into the dependency conflict).

The EoL Node Tests failing are to be expected, as Typescript 5 requires Node 12, and the earliest version of Typedoc that supports TS 5.2 or higher requires Node 16...

Ah, looks like it's not related to Typedoc at all. Typescript 5.0 bumped the minimum Node version to 12, and 5.1 bumped it to 14 [Link](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-5-1.html#breaking-changes) (which explains the cryptic...

> Also, even later versions of typescript can still have their output run by old node versions, the compiler just doesn't run on those versions. A user with node 8...

Given even 5.0 requires a Node 12 or higher at runtime, and we're still supporting Node 8 and 10, should we just skip the Typescript 5 upgrade for the API...

I can confirm by patching the `amazon_msk.py` file to add the following check in [this line](https://github.com/DataDog/integrations-core/blob/amazon_msk-4.9.0/amazon_msk/datadog_checks/amazon_msk/amazon_msk.py#L115) causes the integration to work correctly again: ```python if not 'BrokerNodeInfo' in node_info: continue...