-
Notifications
You must be signed in to change notification settings - Fork 559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: [OSM-1007] fixing a bug causing .NET beta scanning to fail on older versions of .NET #5228
Merged
dotkas
merged 2 commits into
main
from
dotkas/OSM-1007/fix-broken-snyk-nuget-plugin-bug
May 14, 2024
Merged
fix: [OSM-1007] fixing a bug causing .NET beta scanning to fail on older versions of .NET #5228
dotkas
merged 2 commits into
main
from
dotkas/OSM-1007/fix-broken-snyk-nuget-plugin-bug
May 14, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dotkas
force-pushed
the
dotkas/OSM-1007/fix-broken-snyk-nuget-plugin-bug
branch
from
May 8, 2024 19:44
5f5ef98
to
876b6fc
Compare
|
dotkas
force-pushed
the
dotkas/OSM-1007/fix-broken-snyk-nuget-plugin-bug
branch
2 times, most recently
from
May 13, 2024 20:09
31bdf4b
to
4f2dcab
Compare
PeterSchafer
approved these changes
May 14, 2024
The previous version of the plugin had a bug that would cause the scan to fail if running on older versions of the `dotnet` sdk.
dotkas
force-pushed
the
dotkas/OSM-1007/fix-broken-snyk-nuget-plugin-bug
branch
from
May 14, 2024 16:49
4f2dcab
to
bc2751c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The previous version of the plugin had a bug that would cause the scan to fail if running on older versions of the
dotnet
sdk.Pull Request Submission
Please check the boxes once done.
The pull request must:
feat:
orfix:
, others might be used in rare occasions as well, if there is no need to document the changes in the release notes. The changes or fixes should be described in detail in the commit message for the changelog & release notes.Pull Request Review
All pull requests must undergo a thorough review process before being merged.
The review process of the code PR should include code review, testing, and any necessary feedback or revisions.
Pull request reviews of functionality developed in other teams only review the given documentation and test reports.
Manual testing will not be performed by the reviewing team, and is the responsibility of the author of the PR.
For Node projects: It’s important to make sure changes in
package.json
are also affectingpackage-lock.json
correctly.If a dependency is not necessary, don’t add it.
When adding a new package as a dependency, make sure that the change is absolutely necessary. We would like to refrain from adding new dependencies when possible.
Documentation PRs in gitbook are reviewed by Snyk's content team. They will also advise on the best phrasing and structuring if needed.
Pull Request Approval
Once a pull request has been reviewed and all necessary revisions have been made, it is approved for merging into
the main codebase. The merging of the code PR is performed by the code owners, the merging of the documentation PR
by our content writers.
What does this PR do?
PR #5217 introduced a change that would behind-the-scenes call an
MSBuild
command only supported by newer versions of .NET.Where should the reviewer start?
Only packages are changed. The actual bugfix is here: snyk/snyk-nuget-plugin#208 - the tests cover newer versions of .NET.
How should this be manually tested?
npm link
the plugin and run it on one of the fixtures.Any background context you want to provide?
The change was to give a more user-friendly error message to the user, but the scan would still fail.
So the logic is intact, so to speak. This change just re-introduces the original error when executed on older versions of .NET, instead of failing trying to create a user-friendly messaqge.
No new tests have been added, as we're already testing this against new versions of .NET. For older versions of .NET, the plugin will still fail .
What are the relevant tickets?
N/A
Screenshots
N/A
Additional questions
N/A