dotnet(nuget): add missing Sentry.Hangfire - #223
Merged
Conversation
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
BYK
approved these changes
Dec 22, 2025
This was referenced Aug 17, 2026
Lms24
pushed a commit
that referenced
this pull request
Aug 18, 2026
### Context - Same failure mode as #223 (`Sentry.Hangfire`) and #221 (`Sentry.Extensions.AI`) - Follow-up to getsentry/sentry-dotnet#5456 - Tracking issue: getsentry/sentry-dotnet#5495 ### Summary `Sentry.Maui.CommunityToolkit.Mvvm` has shipped on NuGet since 5.8.0 but was never added here. getsentry/sentry-dotnet#5456 added it to sentry-dotnet's `.craft.yml` registry target, and the 6.9.0 publish then aborted ([run 32010411662](https://github.com/getsentry/publish/actions/runs/32010411662)): ``` [error] "name" is required for new package "nuget:Sentry.Maui.CommunityToolkit.Mvvm". Add `name` to the registry target config in your .craft.yml. ``` Craft treats a package as new only when its `latest.json` is missing, so seeding the directory here makes the bare `.craft.yml` key work exactly as it does for the other 18 sentry-dotnet packages. The failure isn't scoped to this one package — `updateVersionInRegistry` throws before craft commits anything, so the whole registry target rolls back. Every sentry-dotnet package is currently still pinned at 6.8.0 here, two releases into 6.9.0 being live on NuGet. ### Notes for review - **Seeded at 6.8.0, not 6.9.0, deliberately.** Craft aborts with `Version file for "6.9.0" already exists. Aborting.` if the version being published is already present — which would roll the target back again and leave all 19 packages stuck at 6.8.0. Seeding the previous version (which the package did ship) lets the retry create 6.9.0 and re-point the symlinks. #223 did the same, seeding `6.0.0-rc.2-prerelease`. - `canonical` has to match the `.craft.yml` key exactly or craft errors on the consistency check in `getUpdatedManifest`. - `created_at` is the value craft wrote for the sibling packages in the 6.8.0 release, since it's the same release event. - Symlinks generated with `bin/sync-links`, not by hand. I also re-ran the full `make sync-all-links` (via `xargs`, as the bare `find` blows the argument limit on macOS) and confirmed it reproduces the committed tree exactly, so the CI sync check should be clean. - No `sdks/sentry.dotnet.maui.communitytoolkit.mvvm` symlink. Every other dotnet package has one, but this package doesn't emit its own `sdk_info.name` — its events go out as `sentry.dotnet.maui` — so the entry would name something nothing reports. Happy to add it if uniformity is preferred. ### Relationship to getsentry/sentry-dotnet#5496 #5496 approaches the same failure from the other side: it gives sentry-dotnet's `.craft.yml` the `name`/`packageUrl`/`mainDocsUrl` that craft needs to create manifests itself — for *every* package, not just this one, so the next new package doesn't repeat this. The two are complementary rather than exclusive. This PR unblocks the 6.9.0 retry now; #5496 stops it happening again. If both land, this package's `.craft.yml` entry is simply belt-and-braces — craft applies the config over the manifest on every release either way. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Context
Sentry.Extensions.AI#222Summary
In
sentry-dotnet, via getsentry/sentry-dotnet#4773,we added the missing
Sentry.Hangfireto the.craft.ymlwhich we forgot to add earlier,so it was missing from the Sentry Release Registry.
Now after adding the missing entry, Craft/Publish is failing because no respective
latest.jsonis available yet.This changeset adds the missing files and symbolic links which are required by Craft/Publish.
Changes
6.0.0-rc.2-prereleaseforSentry.Hangfiremake sync-all-linkspackages/nuget/Sentry.Hangfire/6.0.jsonpackages/nuget/Sentry.Hangfire/6.jsonpackages/nuget/Sentry.Hangfire/latest.jsonFollow-up
registrystep from publish: getsentry/sentry-dotnet@6.0.0 publish#6779