code-server/ci/steps/release-binary.sh

#!/usr/bin/env bash
set -euo pipefail

main() {
  cd "$(dirname "$0")/../.."

  # https://github.com/actions/upload-artifact/issues/38
  tar -xzf release-npm-package/package.tar.gz

  yarn release:binary
  yarn test:binary-release
  yarn package
}

main "$@"
Switch to a single job to build the npm package The architecture specific jobs pull it in and then build releases. Much faster! 2020-05-08 11:48:49 +08:00			`#!/usr/bin/env bash`
			`set -euo pipefail`

			`main() {`
			`cd "$(dirname "$0")/../.."`

Make npm-postinstall.sh more robust 2020-05-13 17:06:11 +08:00			`# https://github.com/actions/upload-artifact/issues/38`
Workaround for GH Actions stripping permissions Closes #1665 2020-05-19 01:48:45 +08:00			`tar -xzf release-npm-package/package.tar.gz`
Make npm-postinstall.sh more robust 2020-05-13 17:06:11 +08:00
Rename static releases to binary releases More clear as discussed in PR. 2020-05-28 03:56:18 +08:00			`yarn release:binary`
			`yarn test:binary-release`
Simplify packaging and improve scripts Much better test now as well. 2020-05-08 12:34:20 +08:00			`yarn package`
Switch to a single job to build the npm package The architecture specific jobs pull it in and then build releases. Much faster! 2020-05-08 11:48:49 +08:00			`}`

			`main "$@"`