Skip to content

Bump packageurl-dotnet from 2.0.0-rc.2 to 2.0.0-rc.3#1737

Merged
JamieMagee merged 1 commit intomainfrom
users/jamagee/package-url-2.0.0-rc.3
Mar 25, 2026
Merged

Bump packageurl-dotnet from 2.0.0-rc.2 to 2.0.0-rc.3#1737
JamieMagee merged 1 commit intomainfrom
users/jamagee/package-url-2.0.0-rc.3

Conversation

@JamieMagee
Copy link
Member

@JamieMagee JamieMagee requested a review from a team as a code owner March 25, 2026 20:21
@JamieMagee JamieMagee requested review from Copilot and melotic March 25, 2026 20:21
@JamieMagee JamieMagee enabled auto-merge (squash) March 25, 2026 20:22
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the centrally managed NuGet dependency version for packageurl-dotnet, which the codebase uses for Package URL (PURL) construction and parsing in component models.

Changes:

  • Bump packageurl-dotnet from 2.0.0-rc.2 to 2.0.0-rc.3 via central package management.

@JamieMagee JamieMagee merged commit cd64b9b into main Mar 25, 2026
25 of 28 checks passed
@JamieMagee JamieMagee deleted the users/jamagee/package-url-2.0.0-rc.3 branch March 25, 2026 21:20
@codecov
Copy link

codecov bot commented Mar 25, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.0%. Comparing base (db2ef16) to head (e594bcf).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@     Coverage Diff      @@
##   main   #1737   +/-   ##
============================
============================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions
Copy link

👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:

  • The detector detects more or fewer components than before
  • The detector generates different parent/child graph relationships than before
  • The detector generates different devDependencies values than before

If none of the above scenarios apply, feel free to ignore this comment 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants