| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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
| Back | FazBrowse Home | New Git URL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality@brunoborges What's the rationale for this change in a patch release? An invalid signature now only fails with verify-signature: true, even though GPG and a valid public key are available
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality@david-allison
If they are available, by default it will warn. To actually verify and fail the build if verification fails, people have to opt-in to the verification. The reason was due to GPG keys rotating from time to time, that would then break builds inadvertently.
You should still see a warning if the key is available and the verification fails.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.