-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
SL Manifest docs & feedback #100
Labels
documentation
Improvements or additions to documentation
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
That's why I'm giving ample time and opportunity to provide feedback. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
Thanks @hilari0n, many of your comments are addressed in the latest spec and reference GH implementation spec. Yes, unsigned manifests was a dumb idea. A central one for all sponsorables was another lousy one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
UPDATED: I've polished a
v2.0.0-rc.1
version of the JWT manifest(s) used by the new SL (both sponsorable and sponsor).Please give it a read and let me know your feedback 🙏: https://www.devlooped.com/SponsorLink/ (source at docs/spec/2.0.0-rc.1.md)
A sample library consuming this new manifest-based SL for testing the end-to-end experience is available at https://www.nuget.org/packages/SponsorableLib.
Please give it a try and provide early feedback.
The text was updated successfully, but these errors were encountered: