This PR removes the 14.12.1-dump1 entries from all .NET package and re-syncs the symlinks so that latest.json points to the latest 4.x stable release.
This version was a preview version and usually, craft should not create any release registry entries for preview versions. However, the chosen suffix isn't supported by craft's preview release detection logic. ~I opened https://github.com/getsentry/craft/pull/561 to add support for it because it seems like a possible suffix to be used in the future.~
I also noticed we have other preview release entries in the nuget/.NET packages like 4.9.0-sync.collectton.2 and 4.12.1-segv1. So to avoid this in the future, we should ensure that we
~either make the check in craft way more wholistic as to what it identifies as a preview release (basically any string after the semver patch number)~
or stick to the defined pre-release suffixes. I just saw that we have some pre-defined suffixes documented for the GitHub craft target but it seems like the same check is used in other craft targets as well. So if we go down this route, we should update the craft documentation accordingly.
bruno-garcia
commented
2 days ago
This PR removes the
14.12.1-dump1entries from all .NET package and re-syncs the symlinks so thatlatest.jsonpoints to the latest 4.x stable release.This version was a preview version and usually, craft should not create any release registry entries for preview versions. However, the chosen suffix isn't supported by craft's preview release detection logic. ~I opened https://github.com/getsentry/craft/pull/561 to add support for it because it seems like a possible suffix to be used in the future.~
I also noticed we have other preview release entries in the nuget/.NET packages like
4.9.0-sync.collectton.2and4.12.1-segv1. So to avoid this in the future, we should ensure that wecloses https://github.com/getsentry/sentry-docs/issues/11716