.github/workflows/ci.yml:41

• [nitpick] If the goal is to pre-fetch dependencies rather than install binaries, using deno cache (e.g., deno cache --no-check) may be more appropriate than deno install --frozen.

        run: deno install --frozen

.github/workflows/ci.yml (2)

60-62: Adopt official Deno setup for format-check
The action is correctly updated to denoland/setup-deno@v2.0.3. For consistency and to accelerate this job (in case remote modules are used), you may optionally enable caching here as well.

-      - name: 🦕 Setup Deno
-        uses: denoland/setup-deno@e95548e56dfa95d4e1a28d6f422fafe75c4c26fb # v2.0.3
+      - name: 🦕 Setup Deno
+        uses: denoland/setup-deno@e95548e56dfa95d4e1a28d6f422fafe75c4c26fb # v2.0.3
+        with:
+          cache: true

---

139-141: Switch to official Deno setup for dry-run-publish
Using denoland/setup-deno@v2.0.3 standardizes the dry-run-publish job. If your publish scripts import remote modules, you can optionally enable cache: true here as well.

-      - name: 🦕 Setup Deno
-        uses: denoland/setup-deno@e95548e56dfa95d4e1a28d6f422fafe75c4c26fb # v2.0.3
+      - name: 🦕 Setup Deno
+        uses: denoland/setup-deno@e95548e56dfa95d4e1a28d6f422fafe75c4c26fb # v2.0.3
+        with:
+          cache: true

.github/workflows/ci.yml (3)

109-112: ⚠️ Potential issue

Replace install step with correct caching command in tests
Swap out deno install --frozen for deno cache --lock=deno.lock to properly fetch and cache the project’s locked dependencies.

Suggested diff:

-        run: deno install --frozen
+        run: deno cache --lock=deno.lock

🤖 Prompt for AI Agents

In .github/workflows/ci.yml at lines 109 to 112, replace the command `deno
install --frozen` with `deno cache --lock=deno.lock` to correctly fetch and
cache the project's locked dependencies during the install step. This ensures
proper dependency caching in the CI workflow.

---

84-87: ⚠️ Potential issue

Fix incorrect dependency pre-caching command in type-check
As above, replace the deno install --frozen invocation with a deno cache step to correctly populate dependencies from the lockfile.

Proposed fix:

-        run: deno install --frozen
+        run: deno cache --lock=deno.lock

🤖 Prompt for AI Agents

In .github/workflows/ci.yml around lines 84 to 87, the command `deno install
--frozen` is incorrectly used for dependency pre-caching. Replace this command
with `deno cache --lock=lock.json --lock-write` or a similar `deno cache`
command that correctly populates dependencies from the lockfile to ensure proper
caching and type-checking.

---

39-42: ⚠️ Potential issue

Fix incorrect dependency installation command
The step deno install --frozen is intended for installing executables and will error out without a target script. To pre-cache project dependencies per your lockfile, use deno cache.

Proposed fix:

-      - name: 📦 Install Dependencies
-        if: ${{ steps.setup-deno.outputs.cache-hit != 'true' }}
-        run: deno install --frozen
+      - name: 📦 Cache Dependencies
+        if: ${{ steps.setup-deno.outputs.cache-hit != 'true' }}
+        run: deno cache --lock=deno.lock

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

      - name: 📦 Cache Dependencies
        if: ${{ steps.setup-deno.outputs.cache-hit != 'true' }}
        run: deno cache --lock=deno.lock

🤖 Prompt for AI Agents

In .github/workflows/ci.yml at lines 39 to 42, the command `deno install
--frozen` is incorrect for installing dependencies and will fail without a
target script. Replace this command with `deno cache --lock=lock.json
--lock-write` (adjust lockfile path if needed) to pre-cache project dependencies
according to the lockfile, ensuring proper dependency installation.