Bump MSTest.TestFramework from 3.2.2 to 3.5.2 · LiorBanai/GitHub-Notifier@714e9b0

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-dotnet@v3.2.0, microsoft/setup-msbuild@v1.3.1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Non-nullable property 'Repo' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Commits' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Possible null reference assignment.

Non-nullable event 'RepositoriesChanged' must contain a non-null value when exiting constructor. Consider declaring the event as nullable.

Non-nullable property 'Repositories' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'LocalGitHubToken' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'GitHubToken' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'RepositoryRoot' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable field 'selectedRepositorySettings' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

Non-nullable field 'Repo' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "artifactory". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Provide feedback