Open GabrielHare opened 1 year ago
@GabrielHare Thanks for submitting the issue. For high level libraries like Cognito, we do not tag release commits. But we do update changelog for each release. If you notice the size of changelog, we release small amount of fixes in each version, as compared to AWS SDK for .NET releases. I can discuss with the team, but not sure if we would decide to maintain release tags.
Thanks, Ashish
Thank you - tracking the change log will provide me with commit hashes to use for version locking, at least for the most recent versions.
Reasons why I would like the project have release tags. (1) This is how I (and probably others) would expect to identify release commits (2) In the case of a scripted git clone (or simply written instructions), the checking out a tag is clearer than checking out a hash
Describe the issue
The latest release of this project on NuGet is 2.4.0 https://www.nuget.org/packages/Amazon.Extensions.CognitoAuthentication/2.4.0
Most of the other versions on NuGet are also not tagged.
Presently there is no tag identifying the commit for this release. Based on commit times I would assume the release commit is on the current latest on master branch. https://github.com/aws/aws-sdk-net-extensions-cognito/commit/4e9f2fad576ada748928837ab9c88abfa23d38e5
Links
No links - this is a an issue with tags, not document files.