Releases: coder/vscode-coder
Releases · coder/vscode-coder
v1.3.9
v1.3.8
- 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, thesession_token
file was renamed tosession
since that is
what the CLI expects.
v1.3.7
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
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
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
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
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
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
Fixed
- Avoid deleting the existing token when launching with a link that omits the
token.
v1.3.0
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.