The package is now being published via a build pipeline in Azure DevOps
I'd like to see this being published via a GitHub Action and only push to NuGet.org when something happens on the master branch.

The feature branches and develop branches can create prerelease packages as an artifact but not publish to NuGet.org

The current API key for publishing to the NuGet feed is expired.
Please create a new one and add it to the secrets of this repository.

With .NET 5, the Azure Functions runtime works in Isolated mode.

Please add support for this configuration in the binding, so we can continue using it.

Hello, there!

As part of the university research we are currently doing regarding the security of Github Actions, we noticed that one or many of the workflows that are part of this repository are referencing vulnerable versions of the third-party actions. As part of a disclosure process, we decided to open issues to notify GitHub Community.

Please note that there are could be some false positives in our methodology, thus not all of the open issues could be valid. If that is the case, please let us know, so that we can improve on our approach. You can contact me directly using an email: ikoishy [at] ncsu.edu

Thanks in advance

1. The workflow main.yml is referencing action gittools/actions/gitversion/setup using references v0.9.7. However this reference is missing the commit 90150b4 which may contain fix to the vulnerability.
2. The workflow main.yml is referencing action gittools/actions/gitversion/execute using references v0.9.7. However this reference is missing the commit 90150b4 which may contain fix to the vulnerability.
3. The workflow new-release.yml is referencing action gittools/actions/gitversion/setup using references v0.9.4. However this reference is missing the commit 90150b4 which may contain fix to the vulnerability.
4. The workflow new-release.yml is referencing action gittools/actions/gitversion/execute using references v0.9.4. However this reference is missing the commit 90150b4 which may contain fix to the vulnerability.

The vulnerability fix that is missing by actions' versions could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider updating the reference to the action.

If you end up updating the reference, please let us know. We need the stats for the paper :-)

The current Action for building a package has a version number defined at several places.

Should be defined as a scoped variable in the action and use it when creating a package & compiling the binaries (AssemblyVersion entries).

Preferably the version is extracted from version control and +1'ed on every build. But other suggestions are welcome.

Add the free Sonarcloud static analysis to the project when building the master branch.

This project and package doesn't has an image or logo attached to the Nuget package.

A simple logo has to be created and added to the package.

At the moment only POST and PUT are supported.
Adding PATCH makes sense, but we'll be using the standard JSON serializer. This way we don't have to assume things what we have to do with partial updates, null values, etc.

This is up to the API or creator of the DTO.