Skip to content

Latest commit

 

History

History
209 lines (129 loc) · 7.04 KB

CHANGELOG.md

File metadata and controls

209 lines (129 loc) · 7.04 KB

Change Log

Unreleased

v1.3.9 (2024-12-12)

  • Only show a login failure dialog for explicit logins (and not autologins).

v1.3.8 (2024-12-06)

  • When starting a workspace, shell out to the Coder binary instead of making an API call. This reduces drift between what the plugin does and the CLI does. As part of this, the session_token file was renamed to session since that is what the CLI expects.

v1.3.7 (2024-11-04)

Added

  • New setting coder.tlsAltHost to configure an alternative hostname to use for TLS verification. This is useful when the hostname in the certificate does not match the hostname used to connect.

v1.3.6 (2024-11-04)

Added

  • Default URL setting that takes precedence over CODER_URL.
  • Autologin setting that automatically initiates login when the extension activates using either the default URL or CODER_URL.

Changed

  • When a client certificate and/or key is configured, skip token authentication.

v1.3.5 (2024-10-16)

Fixed

  • Error messages from the workspace watch endpoint were not logged correctly.
  • Delay notifying about workspaces shutting down since the connection might bump the activity, making the notification misleading.

v1.3.4 (2024-10-14)

Fixed

  • The "All Workspaces" view was not being populated due to visibility check.

Added

  • Log workspaces queries when running with --log=debug.
  • Coder output logs will now have the date prefixed to each line.

v1.3.3 (2024-10-14)

Fixed

  • The plugin no longer immediately starts polling workspaces when connecting to a remote. It will only do this when the Coder sidebar is open.

Changed

  • Instead of monitoring all workspaces for impending autostops and deletions, the plugin now only monitors the connected workspace.

v1.3.2 (2024-09-10)

Fixed

  • Previously, if a workspace stopped or restarted causing the "Start" dialog to appear in VS Code, the start button would fire a start workspace request regardless of the workspace status. Now we perform a check to see if the workspace is still stopped or failed. If its status has changed out from under the IDE, it will not fire a redundant start request.
  • Fix a conflict with HTTP proxies and the library we use to make HTTP requests. If you were getting 400 errors or similar from your proxy, please try again.

Changed

  • Previously, the extension would always log SSH proxy diagnostics to a fixed directory. Now this must be explicitly enabled by configuring a new setting coder.proxyLogDirectory. If you are having connectivity issues, please configure this setting and gather the logs before submitting an issue.

v1.3.1 (2024-07-15)

Fixed

  • Avoid deleting the existing token when launching with a link that omits the token.

v1.3.0 (2024-07-01)

Added

  • If there are multiple agents, the plugin will now ask which to use.

Fixed

  • If the workspace is stopping as the plugin tries to connect, it will wait for the stop and then try to start the workspace. Previously it would only start the workspace if it happened to be in a fully stopped state when connecting.
  • Whenever the plugin wants to start a workspace, it will ask the user first to prevent constantly keeping a workspace up and defeating the point of auto-stop.

v1.2.1 (2024-06-25)

Fixed

  • Fix the update dialog continually reappearing.

v1.2.0 (2024-06-21)

Added

  • New setting coder.proxyBypass which is the equivalent of no_proxy. This only takes effect if http.proxySupport is on or off, otherwise VS Code overrides the HTTP agent the plugin sets.

v1.1.0 (2024-06-17)

Added

  • Workspace and agent statuses now show in the sidebar. These are updated every five seconds.
  • Support http.proxy setting and proxy environment variables. These only take effect if http.proxySupport is on or off, otherwise VS Code overrides the HTTP agent the plugin sets.

v1.0.2 (2024-06-12)

Fixed

  • Redirects will now be followed when watching a workspace build, like when a workspace is automatically started.

v1.0.1 (2024-06-07)

Changed

  • Improve an error message for when watching a build fails.

v1.0.0 (2024-06-05)

Added

  • Support opening workspaces that belong to a different deployment than the one which is currently logged in. This will only work for new connections. If you have an existing connection that errors when connecting because of this, please connect it again using the plugin or the Coder dashboard. Optionally, you may also want to delete your old workspaces from the recents list.

Fixed

  • Escape variables in the header command. If you have a variable in the header command itself, like echo TEST=$CODER_URL, it will now work as expected instead of being substituted with a blank or erroneous value.

v0.1.37 (2024-05-24)

Added

  • openRecent query parameter to open the most recent workspace or directory for that remote.
  • Setting to disable downloading the binary. When disabled, the existing binary will be used as-is. If the binary is missing, the plugin will error.

Fixed

  • Increased timeout will apply to reconnects as well.

Changed

  • Show certificate errors under the token input.

v0.1.36 (2024-04-09)

Changed

  • Automatically update a workspace if required by the template.
  • Show more information when remote setup fails.

Fixed

  • Abort remote connection when remote setup fails.

v0.1.35 (2024-03-12)

Changed

  • Support running within Cursor.

v0.1.34 (2024-03-03)

Changed

  • Improve fetching the Coder binary. This is mostly just better logging but it also will avoid fetching if the existing binary version already matches, to support scenarios where the ETag is ignored.

v0.1.33 (2024-02-20)

Fixed

  • Prevent updating template when automatically starting workspace.