You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #766, the early access workflow publishes, as GitHub early access release, txt and arc files along with the binaries of the artifacts.
Those shouldn't be there.
Expected Behavior
Current Behavior
Steps to Reproduce
Your Environment
Screenshots
The text was updated successfully, but these errors were encountered:
Note this is only for the GitHub release block (not for Maven Central). Having the signatures/checksums with the binaries makes it confusing for users that simply want to download from the GitHub release.
So far, we didn't publish them, as they only show up now after we started signing them for the Scene Builder Kit release to Maven Central.
Is it really confusing for users? I mean, a txt file that does not match the name of the intended artifact (the kit) plus another filename with .asc extension. Alas, it's your prerogative as project maintainer. The good thing is if those files were to be requested by users then enabling is just a quick DSL update away ;-)
After #766, the early access workflow publishes, as GitHub early access release, txt and arc files along with the binaries of the artifacts.
Those shouldn't be there.
Expected Behavior
Current Behavior
Steps to Reproduce
Your Environment
Screenshots
The text was updated successfully, but these errors were encountered: