Keep a changelog about jwt HOT 9 CLOSED

Yes, I'll fill it out for the most recent release too.

from jwt.

Hi Christer,
I think it's a fair ask and would be a good sign of the maturity of the project. It's a one-man show so please don't judge :)
I'll try to keep the record of the changes going forward.

Here's the [Azure DevOps VSRM pipeline](https://dev.azure.com/abatishchev/OpenSource/_releaseDefinition?definitionId=2&_a=definition-tasks&environmentId=2] I'm using to generate a GitHub release before publishing any of the NuGet packages. Any suggestions or improvements are very welcome? Overall, it needs to be replaced with a YAML-based pipeline (see #426k), so any contractions are very welcome too!

from jwt.

Thanks a lot! Would be great if the changelog contains the (user-relevant) changes from 9.0.3 to 10.0.0, too. 🙂

Personally I just keep a manual changelog for all my projects. I have found that to be both simple and adequate.

from jwt.

Would it be possible to just get a quick-and-dirty list of the important changes here, until the changelog is published with this information? At least the breaking changes? I've got alerts nagging me to update the outdated JWT 9.0.3 package... 🙂

from jwt.

Sorry for the delay, I remember about it, will try to get it done today.

The main change and reason for 10.0 was adding System.Text.Json on the platforms where it's supported.

from jwt.

Thanks. I see that the .NET 6 target in the NuGet package also has a dependency on System.Text.Json. That's actually not necessary; .NET 6 has it bundled, so the NuGet dependency on STJ can be removed from that target. (This may also be the case on netstandard2.0; not sure.)

from jwt.

Would you please contribute and make the necessary changes? I'd join and release it asap.

from jwt.

I'll try to do that. Currently setting up a new PC, so may not be able to get to it today.

from jwt.

Would you please contribute and make the necessary changes? I'd join and release it asap.

I see that the project already uses conditions with custom constants (e.g. MODERN_DOTNET) to include/exclude System.Text.Json (among other thing). Since this is non-standard, I will therefore leave it to you to choose how to best adjust the conditions.

Note that netstandard2.0 does not contain STJ. Of the current targets, only net6.0 does.

from jwt.