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
For the lulz, I have a plugin running in some of our pipelines that checks the validity of GPG Keys. With version 2.40.0 of JsonUnit, the GPG Key changed from 0x3F999BB69041CF17E73BB1CEC038787776A19D18 (which has regular Metadata) to 0xEED6202038849B47FEEAD1EC9266326161C26F29 which has no metadata to do a sanity check. Is this intended?
The text was updated successfully, but these errors were encountered:
For the lulz, I have a plugin running in some of our pipelines that checks the validity of GPG Keys. With version 2.40.0 of JsonUnit, the GPG Key changed from 0x3F999BB69041CF17E73BB1CEC038787776A19D18 (which has regular Metadata) to 0xEED6202038849B47FEEAD1EC9266326161C26F29 which has no metadata to do a sanity check. Is this intended?
The text was updated successfully, but these errors were encountered: