[TRI-1281] feat: Add an optional `to` param to `@trigger.dev/cli init update`

[ericallam]

Is your feature request related to a problem? Please describe.

When running npx @trigger.dev/cli@latest update we should allow you to pass in a to option which would set the version to upgrade to (instead of the default which is "latest".

Describe the solution you'd like to see

• Add a to option to the update command, default to "latest":

  trigger.dev/packages/cli/src/cli/index.ts

  Line 98 in e350659

  .action(async (path) => {

• If the to flag isn't "latest" then get ncu to do the change without spitting out the confirmation. There's a flag called upgrade that should work. This file is where edits need to happen:

  trigger.dev/packages/cli/src/commands/update.ts

  Line 35 in e350659

  target: "latest",

_{From SyncLinear.com | TRI-1281}

[RamK777-stack]

@ericallam I have tried, but packages installed versions are same as cli version.

I given npx @trigger.dev/cli@2.1.3 init

Am I missing anything?

[Chigala]

I think it's because you are using the latest CLI @trigger.dev/cli@2.1.3, try using a previous version

[RamK777-stack]

Yes @Chigala you are right. now able to reproduce

[RamK777-stack]

I used same version as cli instead of latest, is this correct ? @ericallam @Chigala

await addDependencies(resolvedPath, [
  { name: "@trigger.dev/sdk", tag: getVersion() },
  { name: "@trigger.dev/nextjs", tag: getVersion() },
]);

Previously it was

  await addDependencies(resolvedPath, [
    { name: "@trigger.dev/sdk", tag: "latest" },
    { name: "@trigger.dev/nextjs", tag: "latest" },
  ]);

[Chigala]

Yeah @RamK777-stack. I think I've got a fix for it.

[matt-aitken]

@Chigala @RamK777-stack thanks for this, really useful info in this and the PR.

There's a major change coming to the CLI: #480. This will be merged in the next couple of days.

This is such a large change that no current CLI PRs will get merged – it would result in tons of conflicts and the underlying code is being changed anyway.

This issue can be worked on after that PR is merged 👍 The method of the fix will be very similar.

[Chigala]

@matt-aitken That's ohk

[matt-aitken]

@ericallam do we definitely want this behaviour? Is there a use case outside of our internal development?

I'm concerned that people who globally install the CLI, unfortunately I think there will be some, will be locked.

Also doesn't it means the message that gets displayed when you run dev will be wrong, as it tells you to run update but that won't work?

[ericallam]

Yea good point, maybe instead could we allow an optional CLI flag to allow specifying the version instead of just a hardcoded latest?