-
Notifications
You must be signed in to change notification settings - Fork 1
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
Link to Release notes from Nuget package? #76
Comments
Hi Sean, We do embed the full release notes into the NuGet package metadata itself, but I wonder if that's not being surfaced properly in Sdkbin 1.0's NuGet feed. They do appear on the Sdkbin gallery automatically though: https://sdkbin.com/publisher/petabridge/product/phobos/packages/phobos.actor/versions/2.5.0 I don't think we'll fix this in Sdkbin 1.0's NuGet mechanism, but I do know for certain it's already fixed in Sdkbin 2.0. 100% agree that we should do this though. |
But one thing I can also start doing is linking to https://phobos.petabridge.com/articles/releases/RELEASE_NOTES.html in each of the subsequent releases - that's where the notes usually go in pretty markdown format (Sdkbin 2.0's gallery will also do this.) |
Interesting -- in all my attempts I didn't wind up at the SDKbin link. Maybe just a muscle memory thing? Both proposed steps sound good to me! |
Just an update on this - we're in the process of getting Sdkbin's infrastructure fixed and this is still on my list of things I want solved. I think we should have this all done by end of January / early Feb 2025. |
We're using RennovateBot to pull in dependency updates (I imagine this is similar for anyone using Dependabot).
I see a new release of Phobos is available, but since I'm a responsible developer, I try to look at what's in a release before merging it (even though I have a higher trust in your Semver commitment than with many other projects).
My current process is something like:
Now, I'm not blameless in this by any means 😅 But it would be great to get a link to the release notes, perhaps as part of the Nuget package metadata itself upon publish. Even a static link to the release notes general page would be helpful.
The text was updated successfully, but these errors were encountered: