fscrypt.git - Go tool for managing Linux filesystem encryption

Age	Commit message (Collapse)	Author
2023-09-09	Bump up required Go version to 1.18	Eric Biggers

2023-01-30	ci.yml: upgrade to actions/checkout@v3	Eric Biggers
	This avoids the following warning from GitHub Actions: Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2.
2022-04-08	Use Go 1.18 in all other CI steps	Joe Richey
	Signed-off-by: Joe Richey <joerichey@google.com>
2022-04-08	Bump up required Go version to 1.16	Eric Biggers
	Bump up the required Go version to 1.16 so that we can assume that Go modules are enabled by default. Go 1.16 is the latest end-of-life release, so this makes it so that we support the latest end-of-life release (1.16), the current maintainance release (1.17), the current release (1.18), and future releases. This the same approach we took when we last bumped up the required Go version. Also update the ci.yml file to test with these versions.
2021-03-31	Only run CI on master branch and PRs to master	Joe Richey
	This avoids duplicate CI checks Signed-off-by: Joe Richey <joerichey@google.com>
2021-03-31	Stop generating and uploading coverage in CI	Joe Richey
	This is currently broken, and we don't really use the findings. Signed-off-by: Joe Richey <joerichey@google.com>
2021-02-02	ci.yml: always run apt-get update	Eric Biggers
	In GitHub Workflows, apparently running 'apt-get update' before 'apt-get install' is sometimes needed, and it doesn't hurt to always do it.
2020-11-26	Switch from Travis CI to GitHub Actions	Eric Biggers
	travis-ci.org is being shut down, so switch to GitHub Actions. It should be mostly equivalent, but I did drop functionality in a couple cases: - Publishing release binaries. I don't think providing Linux binaries is useful, since people build their own anyway. So I left this out. - Build and testing on ppc64le. GitHub Actions only natively supports x86. I tried uraimo/run-on-arch-action, which uses Docker and QEMU user-mode emulation, but the fscrypt tests can't be run because QEMU user-mode emulation doesn't support all the needed system calls.