🚀 Feature Request: Allow specifying Deno version in `deployctl`

[EarlOld]

Problem Description

Currently, deployctl does not allow specifying a specific version of Deno when deploying to Deno Deploy. Instead, the system automatically uses the latest stable version. While this ensures up-to-date deployments, it also creates potential issues when a new Deno release introduces breaking changes or unexpected behavior.

Proposed Solution

Introduce an option in deployctl to specify the desired Deno version explicitly. Possible implementations could be:

• A CLI flag:

  deployctl deploy --deno-version=2.1.9 --project=my-project main.ts
  

• A configuration file (deno.json or deno.jsonc):

  {
    "deploy": {
      "denoVersion": "2.1.9"
    }
  }
  

Why This Matters

• Ensures compatibility with existing projects when new Deno versions introduce changes.
• Allows controlled testing of different Deno versions before upgrading.
• Provides consistency between local development and production environments.

Alternatives Considered

• Using deno upgrade locally before deploying, but this does not affect the version used in Deno Deploy.
• Managing dependencies strictly in import URLs, but this does not help when breaking changes affect the runtime.

Would love to hear your thoughts on whether this feature aligns with Deno Deploy’s vision! 🚀

[hpandelo]

I'm using the following before the build and the deploy steps

      - name: Install Deno
        uses: denoland/setup-deno@v2
        with:
          deno-version: v2.2.3