Releases: buildkite/elastic-ci-stack-for-aws
v6.23.0
v6.23.0 (2024-08-09)
Changed
- Bump agent to v3.77.0 #1355 (@wolfeidau)
Internal
- Dependabot updates: #1354 (@dependabot[bot])
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.23.0/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):
Documentation
v6.22.4
v6.22.4 (2024-07-31)
Changed
- Bump agent to v3.76.2 #1353, #1351 (@DrJosh9000)
- Bump Test Splitter version to v0.8.0 #1349 (@nprizal)
- Upgrade test-splitter-client to v0.7.3 #1344 (@wooly)
Agent Changelog
v3.76.2 (2024-08-01)
[!NOTE]
v3.76.0 fixed an issue which caused the HTTP client in the agent to fall back to HTTP/1.1, see #2908. If you need to disable HTTP/2.0 in your environment you can do this using the--no-http2
flag or matching configuration option.
Fixed
- Only override TLSClientConfig if set #2913 (@DrJosh9000)
v3.76.1 (2024-07-31)
[!NOTE]
v3.76.0 fixed an issue which caused the HTTP client in the agent to fall back to HTTP/1.1, see #2908. If you need to disable HTTP/2.0 in your environment you can do this using the--no-http2
flag or matching configuration option.
Changed
- Pass cancel grace period to bootstrap #2910 (@DrJosh9000)
v3.76.0 (2024-07-31)
[!NOTE]
This release fixed an issue which caused the HTTP client in the agent to fall back to HTTP/1.1, see #2908. If you need to disable HTTP/2.0 in your environment you can do this using the--no-http2
flag or matching configuration option.
Changed
- fix enable http/2 by default as intended by flags #2908 (@wolfeidau)
Fixed
- Let artifact phase and post-command run in grace period #2899 (@DrJosh9000)
Internal
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.22.4/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):
Documentation
v6.22.3
v6.22.3 (2024-07-22)
Changed
- Bump Agent to v3.75.1 and Scaler to v1.8.0 #1345 (@DrJosh9000)
Note
Depending on how you upgrade existing stacks, you may not automatically be upgraded to v1.8.0 of Buildkite Agent Scaler. A work around exists for this known issue.
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.22.3/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):
Documentation
v6.22.2
v6.22.2 (2024-07-18)
Changed
- Bump agent version to v3.75.0 #1342 (@wolfeidau)
Added
Dependencies
- Bump golang.org/x/sys from 0.21.0 to 0.22.0 #1340 (@dependabot[bot])
Agent Changelog
Added
- Introduce
riscv64
architecture #2877 (@TimePrinciple) - Add a SHA256SUMS file #2890 (@DrJosh9000)
Changed
- Reject more secrets #2884 (@DrJosh9000)
- Include repo name in Packages image path #2871 (@swebb)
Fixed
- Fix some common artifact download bugs #2878 (@DrJosh9000)
- SUP-2343: remove "retry" example from "buildkite-agent step get" as not valid #2879 (@tomowatt)
Internal
- Log in to buildkite packages right before pushing images #2892 (@moskyb)
- Update LICENSE.txt #2885 (@wooly)
- Remove Packagecloud agent publish steps from agent pipeline #2873 (@tommeier)
- Release Docker images on Buildkite Packages #2837 (@swebb)
- Fix the OIDC login for Packages #2875 (@swebb)
- Fix the Packages registry name #2874 (@swebb)
- Fix image name when pushing to Buildkite packages #2870 (@swebb)
- Dependabot updates: #2888, #2887, #2882, #2883, #2880 (@dependabot[bot])
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.22.2/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):
Documentation
v6.22.1
v6.22.1 (2024-07-04)
Changed
- bump the agent version to v3.74.1 #1338 (@wolfeidau)
Internal
- Create dependabot.yml, update some Go things #1332 (@DrJosh9000)
Agent Changelog
Added
- Log public signing key thumbprint and signed step payload #2853 (@jordandcarter)
Fixed
- Don't try to early-set env vars #2852 (@DrJosh9000)
- Convey env vars between k8s containers #2851 (@DrJosh9000)
- Fix typo in "kuberentes" #2836 (@moskyb)
Internal
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.22.1/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):
Documentation
v6.22.0
v6.22.0 (2024-06-19)
Added
Changed
Agent Changelog
Security
⚠️ When usingartifact download
, artifacts that were uploaded with paths containing..
will no longer be able to traverse up from the destination path. This change is unlikely to break the vast majority of pipelines, however if you are relying on..
for path traversal and cannot fix your pipeline, you can enable the new experimentallow-artifact-path-traversal
#2815 (@DrJosh9000)- Redact Job API token like other env vars #2834 (@DrJosh9000)
Added
- Add logs to allowed-[repositories|plugins] #2810 (@jakubm-canva)
Fixed
- Fix error in k8s after job completes #2804 (@DrJosh9000)
Changed
Internal
- kubernetes-exec is now a flag #2814 (@DrJosh9000)
- shell logger: Use fmt functions once #2805 (@DrJosh9000)
- Update deprecated import #2811 (@DrJosh9000)
- Use Rand per-test in agent/plugin/error_test.go #2795 (@moskyb)
- Publish debian and rpm packages to Buildkite Packages #2824 #2826 #2831 #2830 #2833 (@sj26)
- Dependabot updates: #2809, #2816, #2800, #2801, #2802, #2803, #2787, #2798, #2808, #2827 #2817, #2818, #2819, #2822, #2829, #2832, #2835 (@dependabot[bot])
Important
When using artifact download
, artifacts that were uploaded with paths containing ..
will no longer be able to traverse up from the destination path. This change is unlikely to break the vast majority of pipelines, however if you are relying on ..
for path traversal and cannot fix your pipeline, you can enable the new experiment allow-artifact-path-traversal
Fixed
- Lazy-unmount /tmp before masking #1327 (@DrJosh9000)
Dependencies
- Bump Docker buildx to v0.15.0 #1329 (@rianmcguire)
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.22.0/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):
Documentation
v6.21.0
v6.21.0 (2024-05-27)
Changed
- Bump agent version to 3.73.1 #1323 #1321 #1320 (@DrJosh9000 + @moskyb)
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.21.0/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):
Documentation
v6.20.0
6.20.0 (2024-05-03)
Fixed
- Fix windows agent not restarting #1318 (@patrobinson)
Dependencies
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.20.0/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):
Documentation
v6.19.0
v6.19.0 (2024-04-30)
Changed
- Bump agent version #1314 (@patrobinson)
- Only allow SSH to reach Packer instance from Elastic Stack #1308 (@steveh)
- Restore "Packer Builder" tag for Packer instances #1307 (@steveh)
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.19.0/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):
Documentation
v6.18.0
v6.18.0 (2024-03-28)
Changed
- Bump agent version to v3.67.0 #1303 (@DrJosh9000)
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.18.0/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):