fscrypt.git/.github/workflows, branch v0.3.5 Go tool for managing Linux filesystem encryption ci.yml: use actions/checkout@v4 2024-02-07T06:19:57+00:00 Eric Biggers ebiggers@google.com 2024-02-07T05:15:38+00:00 d00b4634290f2190a430720b2e444c3a1a2d5a42 This addresses the following warning from GitHub Actions: Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/. A near-identical warning forced everyone to upgrade to v3 last year, so this is some pointless churn, but let's just get it over with again... 
This addresses the following warning from GitHub Actions:

    Node.js 16 actions are deprecated. Please update the following
    actions to use Node.js 20: actions/checkout@v3. For more information
    see:
    https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

A near-identical warning forced everyone to upgrade to v3 last year, so
this is some pointless churn, but let's just get it over with again...
Bump up required Go version to 1.18 2023-09-09T22:54:30+00:00 Eric Biggers ebiggers@google.com 2023-09-09T22:52:08+00:00 43869584b3c9f9acade09d2d35b20e69623d98f8 






ci.yml: upgrade to actions/checkout@v3
2023-01-31T06:59:20+00:00

Eric Biggers
ebiggers@google.com

2023-01-31T06:59:20+00:00

d7ec9dc02acaf6bfd6c79928eb665506c4b6c63c

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.





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.







Use Go 1.18 in all other CI steps
2022-04-08T23:36:23+00:00

Joe Richey
joerichey@google.com

2022-04-08T23:36:23+00:00

a224e769a478cc446c05dbfd5eb7e32d31933172

Signed-off-by: Joe Richey <joerichey@google.com>





Signed-off-by: Joe Richey <joerichey@google.com>







Bump up required Go version to 1.16
2022-04-08T23:08:12+00:00

Eric Biggers
ebiggers@google.com

2022-04-08T22:55:58+00:00

657a1f0f44b61725f1b8041bceef6f262ffcb770

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.





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.







Only run CI on master branch and PRs to master
2021-03-31T23:00:16+00:00

Joe Richey
joerichey@google.com

2021-03-31T23:00:16+00:00

c3bb6c7d9304894a35a2229f4ceda76f745fc264

This avoids duplicate CI checks

Signed-off-by: Joe Richey <joerichey@google.com>





This avoids duplicate CI checks

Signed-off-by: Joe Richey <joerichey@google.com>







Stop generating and uploading coverage in CI
2021-03-31T22:55:39+00:00

Joe Richey
joerichey@google.com

2021-03-31T22:46:18+00:00

2fa66887a238311a026f44b40ec1b1d876ec3cfd

This is currently broken, and we don't really use the findings.

Signed-off-by: Joe Richey <joerichey@google.com>





This is currently broken, and we don't really use the findings.

Signed-off-by: Joe Richey <joerichey@google.com>







ci.yml: always run apt-get update
2021-02-03T00:40:46+00:00

Eric Biggers
ebiggers@google.com

2021-02-03T00:14:30+00:00

7fa623a0c9fe043ab709e48f43d1fc44f51f5f5a

In GitHub Workflows, apparently running 'apt-get update' before 'apt-get
install' is sometimes needed, and it doesn't hurt to always do it.





In GitHub Workflows, apparently running 'apt-get update' before 'apt-get
install' is sometimes needed, and it doesn't hurt to always do it.







Switch from Travis CI to GitHub Actions
2020-11-26T09:08:36+00:00

Eric Biggers
ebiggers@google.com

2020-11-21T23:29:26+00:00

0692c00a2af75a5ec6c26e58adb37fa152912dce

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.





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.