Add mention of Remote Development changelog
This commit is contained in:
gregvanl
Родитель
b74b1558b6
Коммит
67bc43584a
|
|
@ -215,7 +215,7 @@ Multi-line commands now display a new line symbol where appropriate and will als
|
|||
|
||||
Here are the smaller improvements to shell integration:
|
||||
|
||||
* Command navigation has improved visual feedback, showing the "focus border" briefly and then keeping a persistent rectangle in the gutter to help better orient the user after jumping around the buffer.
|
||||
* Command navigation has improved visual feedback, showing the "focus border" briefly and then keeping a persistent rectangle in the gutter to help highlight the position in the buffer.
|
||||
|
||||
|
||||
|
||||
|
|
@ -451,6 +451,12 @@ There has been more progress on the [GitHub Pull Requests and Issues](https://ma
|
|||
|
||||
Check out the [changelog for the 0.48.0](https://github.com/microsoft/vscode-pull-request-github/blob/main/CHANGELOG.md#0480) release of the extension to see the other highlights.
|
||||
|
||||
### Remote Development
|
||||
|
||||
Work continues on the [Remote Development extensions](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack), which allow you to use a container, remote machine, or the [Windows Subsystem for Linux](https://docs.microsoft.com/windows/wsl) (WSL) as a full-featured development environment.
|
||||
|
||||
You can learn about new extension features and bug fixes in the [Remote Development release notes](https://github.com/microsoft/vscode-docs/blob/main/remote-release-notes/v1_70.md).
|
||||
|
||||
## Preview features
|
||||
|
||||
### Editor Sticky scroll
|
||||
|
|
|
|||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:91fa228815927cd9ed9a6805a7c1d47e70d195a5e2deac9a77074af767519bb7
|
||||
size 46234
|
||||
|
|
@ -1,38 +1,38 @@
|
|||
# July 2022 (version 1.70)
|
||||
|
||||
## Core
|
||||
|
||||
## Development Containers
|
||||
|
||||
We continue work across the Remote-Containers extension and the open [dev container specification](https://containers.dev/), which seeks to allow anyone in any tool (including ones other than VS Code) to use containers for their inner and outer loop activities. Its reference implementation is the [dev container CLI](https://github.com/devcontainers/cli).
|
||||
We continue work across the Remote - Containers extension and the open [dev container specification](https://containers.dev/), which seeks to allow anyone in any tool (including ones other than VS Code) to use containers for their inner and outer loop activities. Its reference implementation is the [dev container CLI](https://github.com/devcontainers/cli).
|
||||
|
||||
|
||||
|
||||
|
||||
### Dev container features
|
||||
### Dev container Features
|
||||
|
||||
Dev container "Features" are a preview feature of dev containers consisting of self-contained units of installation code and configuration. We've been [iterating](https://github.com/devcontainers/cli/pull/73) on our initial Features implementation, and [the latest has been merged into the spec repo](https://github.com/devcontainers/spec/blob/main/proposals/devcontainer-features.md) and the dev container CLI.
|
||||
Dev container **Features** are a preview option of dev containers consisting of self-contained units of installation code and configuration. We've been [iterating](https://github.com/devcontainers/cli/pull/73) on our initial Features implementation, and [the latest has been merged into the spec repo](https://github.com/devcontainers/spec/blob/main/proposals/devcontainer-features.md) and the dev container CLI.
|
||||
|
||||
We've also merged an [updated proposal for distributing features and templates](https://github.com/devcontainers/spec/blob/main/proposals/devcontainer-features-distribution.md), now with the ability to upload them as [OCI Artifacts in registries](https://github.com/devcontainers/spec/blob/main/proposals/devcontainer-features-distribution.md#oci-registry). We are working toward getting this into the CLI, and we welcome any feedback on the proposal via GitHub [issues](https://github.com/devcontainers/spec/issues) or [Discussions](https://github.com/devcontainers/spec/discussions).
|
||||
We've also merged an [updated proposal for distributing features and templates](https://github.com/devcontainers/spec/blob/main/proposals/devcontainer-features-distribution.md), now with the ability to upload them as [OCI Artifacts in registries](https://github.com/devcontainers/spec/blob/main/proposals/devcontainer-features-distribution.md#oci-registry). We are working toward getting this into the CLI, and we welcome any feedback on the proposal via GitHub [Issues](https://github.com/devcontainers/spec/issues) or [Discussions](https://github.com/devcontainers/spec/discussions).
|
||||
|
||||
### Dev container CLI
|
||||
|
||||
The CLI [now supports](https://github.com/devcontainers/cli/pull/61) multiple `--image-name` parameters, such as: `devcontainer build --workspace-folder ./ --image-name alpine3 --image-name alpine3.0`. This allows you to tag the same image more than once, which is especially helpful for tagging multi-architecture images.
|
||||
The CLI [now supports](https://github.com/devcontainers/cli/pull/61) multiple `--image-name` parameters, such as:
|
||||
|
||||
```bash
|
||||
`devcontainer build --workspace-folder ./ --image-name alpine3 --image-name alpine3.0`
|
||||
```
|
||||
|
||||
This allows you to tag the same image more than once, which is especially helpful for tagging multi-architecture images.
|
||||
|
||||
We've added the ability to [test features](https://github.com/devcontainers/cli/pull/81) from the CLI with `devcontainer features test`. Below is an example of this command:
|
||||
|
||||
|
||||
|
||||
|
||||
There was also a [bug fix](https://github.com/microsoft/vscode-remote-release/issues/6913) to allow falling back to `id -u -n` in the case the container can't find a username.
|
||||
There was also a [bug fix](https://github.com/microsoft/vscode-remote-release/issues/6913) to allow falling back to `id -u -n` in the case when the container can't find a username.
|
||||
|
||||
### Remote-Containers
|
||||
### Remote - Containers
|
||||
|
||||
We [introduced a fix](https://github.com/devcontainers/cli/issues/83) so that copying a file with executable permissions (such as the dev container CLI executable) preserves the executable bit on the file permissions.
|
||||
We [made a fix](https://github.com/devcontainers/cli/issues/83) so that copying a file with executable permissions (such as the dev container CLI executable) preserves the executable bit on the file permissions.
|
||||
|
||||
The latest in dev container features and the CLI will also be landing in Remote-Containers this release.
|
||||
|
||||
## SSH
|
||||
|
||||
## WSL
|
||||
The latest in dev container features and the CLI will also be landing in Remote - Containers this release.
|
||||
|
||||
## The Visual Studio Code Server (private preview)
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче