Skip to content

Releases: denoland/deployctl

1.12.0

14 Mar 18:56
612f83d
Compare
Choose a tag to compare

What's Changed

Full Changelog: 1.11.0...1.12.0

1.11.0

01 Mar 01:06
1e16376
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.10.5...1.11.0

1.10.5

14 Feb 11:54
6dce4af
Compare
Choose a tag to compare

What's Changed

New Contributors

1.10.4

08 Feb 11:40
3d0ba0f
Compare
Choose a tag to compare

What's Changed

  • chore: Bump MINIMUM_DENO_VERSION by @arnauorriols in #255
  • fix: Fallback to manual navigation when opening the browser automatically during token provisioning fails by @arnauorriols in #256
  • fix: Windows support for automatic token provisioning by @arnauorriols in #257

Full Changelog: 1.10.3...1.10.4

1.10.3

26 Jan 01:22
f21311b
Compare
Choose a tag to compare

What's Changed

Full Changelog: 1.10.2...1.10.3

1.10.2

25 Jan 21:25
9085102
Compare
Choose a tag to compare

What's Changed

Full Changelog: 1.10.1...1.10.2

1.10.1

22 Jan 15:53
1d25e56
Compare
Choose a tag to compare

What's Changed

Full Changelog: 1.10.0...1.10.1

1.10.0

22 Jan 12:18
c55f803
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.9.1...1.10.0

1.9.1

04 Jan 10:58
7a82532
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.9.0...1.9.1

1.9.0

01 Dec 14:11
48c9c67
Compare
Choose a tag to compare

deployctl 1.9.0: token provisioning, config file, and much more!

With the 1.9.0 release of deployctl, manual access-token handling is a thing of
the past! 🎉 Starting with this release, if a token is not provided via arg or
env, a new one will be provisioned using an OAuth authorization flow.

Additionally, several other improvements have been introduced to simplify the
user experience of the tool: this version introduces support for a config file
where some settings like project, entrypoint, include and exclude can be
configured and shared. This config file is created at the end of a deployment if
it does not exist yet. It defaults to deno.json (integrating with the rest of
deno CLI configuration), and looks like this:

{
  ...
  "deploy": {
    "project": "6067570b-ee11-4e2e-b7df-692d11e049d5",
    "exclude": [],
    "include": [
      "main.ts",
      "deps.ts"
    ],
    "entrypoint": "main.ts"
  }
}

You can continue to perform deployments using the --entrypoint and --project
flags (which now will create the project automatically during deployment if it
does not exist). However, we have introduced some heuristics to try and make
deployments even more simple. Now deployctl guesses the project name of the
deployment based on the Git repository it is in (or directory name if the
deployment is not performed within a repository). Similarly, it guesses the
entrypoint by looking for files with common entrypoint names (main.ts,
src/main.ts, etc), so that, most of the time, having your code deployed around
the globe can be as simple as running:

deployctl deploy

What's Changed

New Contributors

Full Changelog: 1.8.2...1.9.0