1484bee621
* wip: changelog * fixup * fix: add +x to product.json in build-vscode While testing a pre-release, there seems to be a bug with the file permissions for `product.json`. Adding `chmod +x` to see if that fixes it. * chore: increase timeout * fix: keep product.json file permissions in release When we added the change to modify the `package.json` version using `mv` and `jq` we didn't account for lost file permissions. This caused a bug only happening in CI. This should fix it by giving it 755 via `chmod`. * trigger ci * chore: update package.json bust cache * fixup!: fix: keep product.json file permissions in release * Revert "fix: add +x to product.json in build-vscode" This reverts commit fc4d2b532f41277d6b93243cd6bd2ba2434f80d6. * chore: pin ubuntu runner in build code-server * chore: update prettierignore * chore: add notes to changelog * chore: use ubuntu-22.04 for e2e * chore: pin all jobs in build to ubuntu 20.04 * feat(wrapper): add tests for isChild * fixup: include description ts-expect-error comment * chore: update CHANGELOG * chore: update Helm chart * fixup: use our childProcess * Update CHANGELOG.md Co-authored-by: Asher <ash@coder.com> Co-authored-by: Asher <ash@coder.com>
24 lines
1.1 KiB
YAML
24 lines
1.1 KiB
YAML
apiVersion: v2
|
|
name: code-server
|
|
description: A Helm chart for coder/code-server
|
|
|
|
# A chart can be either an 'application' or a 'library' chart.
|
|
#
|
|
# Application charts are a collection of templates that can be packaged into versioned archives
|
|
# to be deployed.
|
|
#
|
|
# Library charts provide useful utilities or functions for the chart developer. They're included as
|
|
# a dependency of application charts to inject those utilities and functions into the rendering
|
|
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
|
|
type: application
|
|
|
|
# This is the chart version. This version number should be incremented each time you make changes
|
|
# to the chart and its templates, including the app version.
|
|
# Versions are expected to follow Semantic Versioning (https://semver.org/)
|
|
version: 3.4.0
|
|
|
|
# This is the version number of the application being deployed. This version number should be
|
|
# incremented each time you make changes to the application. Versions are not expected to
|
|
# follow Semantic Versioning. They should reflect the version the application is using.
|
|
appVersion: 4.9.0
|