Skip to content

Commit abb32bd

Browse files
fix: Await verify function (#629)
After bumping `snaps-registry`, `verify` needs to be awaited. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk: this is a one-line build-time fix to correctly await `verify`, affecting only registry signature validation flow during Gatsby sourcing. > > **Overview** > Fixes registry signature validation during the Gatsby build by awaiting the now-async `verify` call before asserting validity. > > This ensures the `Invalid registry signature` check uses the resolved boolean result rather than a pending Promise after the `snaps-registry` dependency update. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 03e0579. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
1 parent a14b647 commit abb32bd

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

gatsby-node.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ async function getRegistry() {
138138
headers: HEADERS,
139139
}).then(async (response) => response.json());
140140

141-
const isRegistryValid = verify({
141+
const isRegistryValid = await verify({
142142
registry: rawRegistry,
143143
signature,
144144
publicKey: PUBLIC_KEY,

0 commit comments

Comments
 (0)