We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@joelverhagen commented on Tue Jul 17 2018
When a package must be signed, we can quickly reject an unsigned version by checking for the presence of a signature file.
When a package must not be signed, we can quickly reject a signed version by checking for the presence of a signature file.
Both operations are safe to be done in gallery process.
I need text for both cases and for both the upload flow and the command line push flow.
/cc @anangaur
The text was updated successfully, but these errors were encountered:
Add IsSigningAllowed method (#6199)
c878ae0
Progress on #6181
Proposed strings for both web UI and command line.
When publishing an unsigned package and signing is required:
This package must be signed with a registered certificate.
When publishing a signed package and no certificate is configured.
The package was signed. You must register the signing certificate to publish signed packages.
@anangaur?
Sorry, something went wrong.
Reject packages that don't meet the owner/ID signing requirements (#6210
c2c34de
) Address #6181
320a80e
50f4335
joelverhagen
No branches or pull requests
@joelverhagen commented on Tue Jul 17 2018
When a package must be signed, we can quickly reject an unsigned version by checking for the presence of a signature file.
When a package must not be signed, we can quickly reject a signed version by checking for the presence of a signature file.
Both operations are safe to be done in gallery process.
@joelverhagen commented on Tue Jul 17 2018
I need text for both cases and for both the upload flow and the command line push flow.
/cc @anangaur
The text was updated successfully, but these errors were encountered: