diff --git a/test/jest_link.ts b/test/jest_link.ts
index fc349a5698..9996fd9c3c 100644
--- a/test/jest_link.ts
+++ b/test/jest_link.ts
@@ -1,26 +1,14 @@
 import { execSync } from 'child_process';
 import { join, resolve } from 'path';
 
-// TODO remove install and link after https://github.com/demergent-labs/azle/issues/1807 is resolved
+// TODO remove linkAndInstallPatch after https://github.com/demergent-labs/azle/issues/1807 is resolved
 export function linkAndInstallPatch(pathRelativeToAzle: string): void {
     const examplesDir =
         process.env.GITHUB_WORKSPACE ?? resolve(__dirname, '..');
 
-    console.log('examplesDir', examplesDir);
-
-    console.log(
-        'process.env.AZLE_END_TO_END_TEST_LINK_AZLE',
-        process.env.AZLE_END_TO_END_TEST_LINK_AZLE
-    );
-
-    // TODO do we even need to do this on release?
     execSync(`cd ${join(examplesDir, pathRelativeToAzle)} && npm install`);
 
     if (process.env.AZLE_END_TO_END_TEST_LINK_AZLE !== 'false') {
-        // TODO remove logs once we are satisfied that the link doesn't happen during release candidate tests
-        console.log('--------------------------------------------------------');
-        console.log("--- We're linking!!! -----------------------------------");
-        console.log('--------------------------------------------------------');
         execSync(
             `cd ${join(examplesDir, pathRelativeToAzle)} && npm link azle`
         );