hermetic_cc_toolchain/ci/release

#!/usr/bin/env bash

# Copyright 2023 Uber Technologies, Inc.
# Licensed under the MIT License

set -xeuo pipefail

cd "$(git rev-parse --show-toplevel)"
prev_ref=$(git rev-parse HEAD)
git commit --allow-empty -m "this is a test commit"
tools/bazel run //tools/releaser -- -tag v99.0.0
cleanup() { git tag -d v99.0.0; git reset --hard "$prev_ref"; }
trap cleanup EXIT

file hermetic_cc_toolchain-v99.0.0.tar.gz | grep -q 'gzip compressed data'
misc: use /usr/bin/env in scripts This patch continues the work to support NixOS and others non-FHS distributions by replacing instances of `/bin/bash` with `/usr/bin/env bash`, which works correctly in more systems than the former. Signed-off-by: Luis Holanda <luiscmholanda@gmail.com> 2022-07-27 23:33:53 +03:00			`#!/usr/bin/env bash`
Re-license portions of the code to Apache 2.0 Your old version of the software released under the old license can still be used under the terms of the old license. I have received the following statement from the past contributors Luis Holanda, Jeremy Volkman and Fabian Hahn: I hereby confirm that I am the copyright holder or authorized by the copyright holder of this contribution. As such I hereby confirm that all contributions made to bazel-zig-cc by me or on behalf of me, hereby is licensed under the Apache 2.0 License [http://www.apache.org/licenses/LICENSE-2.0]. I am aware that my previous contributions will still be available under the MIT license as well. I confirm that I am aware of the bazel-zig-cc teams intention to release bazel-zig-cc under the Apache 2.0 License from release [1.0] and onwards, and that the bazel-zig-cc no longer will accept contributions made under the MIT and that any future submissions from myself will be considered to be licensed under Apache 2.0 unless I expressly state otherwise. Copyright and re-licensing for Google and Uber employees has been resolved internally. Since not all contributors took action to re-license the code yet, portions of bazel-zig-cc remain licensed as MIT. I have started this project during my personal time with my personal resources. I am now handing over all copyrights to this code to Uber Technologies, Inc. 2023-03-02 23:42:35 +02:00
			`# Copyright 2023 Uber Technologies, Inc.`
revert "Re-license portions of the code to Apache 2.0" (#35) This (partially) reverts commit dfdb1f26805c1ccf6d1113276d40c8ce4c1fa17e 2023-04-20 03:23:25 +03:00			`# Licensed under the MIT License`
Re-license portions of the code to Apache 2.0 Your old version of the software released under the old license can still be used under the terms of the old license. I have received the following statement from the past contributors Luis Holanda, Jeremy Volkman and Fabian Hahn: I hereby confirm that I am the copyright holder or authorized by the copyright holder of this contribution. As such I hereby confirm that all contributions made to bazel-zig-cc by me or on behalf of me, hereby is licensed under the Apache 2.0 License [http://www.apache.org/licenses/LICENSE-2.0]. I am aware that my previous contributions will still be available under the MIT license as well. I confirm that I am aware of the bazel-zig-cc teams intention to release bazel-zig-cc under the Apache 2.0 License from release [1.0] and onwards, and that the bazel-zig-cc no longer will accept contributions made under the MIT and that any future submissions from myself will be considered to be licensed under Apache 2.0 unless I expressly state otherwise. Copyright and re-licensing for Google and Uber employees has been resolved internally. Since not all contributors took action to re-license the code yet, portions of bazel-zig-cc remain licensed as MIT. I have started this project during my personal time with my personal resources. I am now handing over all copyrights to this code to Uber Technologies, Inc. 2023-03-02 23:42:35 +02:00
[release] add to CI 2022-04-18 12:35:14 +03:00			`set -xeuo pipefail`

			`cd "$(git rev-parse --show-toplevel)"`
fix ci/release by adding a stub commit there 2022-04-20 14:45:48 +03:00			`prev_ref=$(git rev-parse HEAD)`
			`git commit --allow-empty -m "this is a test commit"`
replace zopfli with encoding/gzip 2023-03-14 10:15:43 +02:00			`tools/bazel run //tools/releaser -- -tag v99.0.0`
			`cleanup() { git tag -d v99.0.0; git reset --hard "$prev_ref"; }`
shellcheck 2022-04-18 12:35:14 +03:00			`trap cleanup EXIT`
[release] add to CI 2022-04-18 12:35:14 +03:00
Rename bazel-zig-cc to hermetic_cc_toolchain (#36) As it says on the tin. Long live hermetic_cc_toolchain! 2023-04-21 17:00:03 +03:00			`file hermetic_cc_toolchain-v99.0.0.tar.gz \| grep -q 'gzip compressed data'`