Skip to content

Updating buildpacks in buildpack.toml #669

Updating buildpacks in buildpack.toml

Updating buildpacks in buildpack.toml #669

Triggered via push August 4, 2024 06:24
Status Success
Total duration 9m 6s
Artifacts
Get Builders for Testing
3s
Get Builders for Testing
Matrix: Integration Tests
Alert on Failure
0s
Alert on Failure
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Get Builders for Testing
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Integration Tests (index.docker.io/paketobuildpacks/builder:buildpackless-full)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v3, actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Integration Tests (index.docker.io/paketobuildpacks/builder-jammy-buildpackless-full:latest)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v3, actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Release
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/