Skip to content

feat: support if-none-match for the extension list endpoint #159

feat: support if-none-match for the extension list endpoint

feat: support if-none-match for the extension list endpoint #159

Triggered via pull request March 14, 2026 15:36
Status Success
Total duration 6m 19s
Artifacts 1

ci.yml

on: pull_request
extension-ci  /  Build Docker Images
2m 15s
extension-ci / Build Docker Images
extension-ci  /  Test Helm Charts
19s
extension-ci / Test Helm Charts
extension-ci  /  Build Linux Packages
extension-ci / Build Linux Packages
extension-ci  /  Bump Chart Patch Version on main branch
0s
extension-ci / Bump Chart Patch Version on main branch
extension-ci  /  Trigger test environment updates
0s
extension-ci / Trigger test environment updates
extension-ci  /  Check Module Download on Tag
0s
extension-ci / Check Module Download on Tag
extension-ci  /  ...  /  Snyk
extension-ci / [Release] Snyk Monitor latest / Snyk
extension-ci  /  Release Helm Chart
0s
extension-ci / Release Helm Chart
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
extension-ci / Audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: sonarsource/sonarqube-scan-action@v7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
extension-ci / Test Helm Charts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
extension-ci / Test Helm Charts
No file matched to [/home/runner/work/extension-appdynamics/extension-appdynamics/**/*requirements*.txt,/home/runner/work/extension-appdynamics/extension-appdynamics/**/*requirements*.in,/home/runner/work/extension-appdynamics/extension-appdynamics/**/*constraints*.txt,/home/runner/work/extension-appdynamics/extension-appdynamics/**/*constraints*.in,/home/runner/work/extension-appdynamics/extension-appdynamics/**/pyproject.toml,/home/runner/work/extension-appdynamics/extension-appdynamics/**/uv.lock,/home/runner/work/extension-appdynamics/extension-appdynamics/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.

Artifacts

Produced during runtime
Name Size Digest
steadybit~extension-appdynamics~OJGKX8.dockerbuild
68.2 KB
sha256:45793a216550e7eb00ee16ede3eee87e1a4606fff5a47ff780a3cd814fb425ab