fix(docker-base): skip curl include symlink when target already exists#19

Merged

nathanaelytj merged 2 commits into

fix/curl-symlink-guard

Jun 5, 2026

nathanaelytj commented Jun 5, 2026

Member

The curl header symlink step copied from the official php image fails
in dunglas/frankenphp:1-builder-php8.5 because /usr/local/include/curl
already exists there, aborting the php-recompile stage under set -e:

ln: failed to create symbolic link '/usr/local/include/curl': File exists

Guard on the target path as well, so the ln is skipped when the
builder image already provides the include directory.

Fixes the image-base-build failure from run 26995756119.


          fix(docker-base): skip curl include symlink when target already exists

0b8efe6

The curl header symlink step copied from the official php image fails
in dunglas/frankenphp:1-builder-php8.5 because /usr/local/include/curl
already exists there, aborting the php-recompile stage under set -e:

  ln: failed to create symbolic link '/usr/local/include/curl': File exists

Guard on the target path as well, so the ln is skipped when the
builder image already provides the include directory.

nathanaelytj enabled auto-merge (squash)

June 5, 2026 04:45


          ci(codacy): assign unique SARIF run categories before upload

da99121

The CodeQL upload-sarif action now rejects SARIF files that contain
multiple runs sharing the same category (derived from
automationDetails.id), blocking the required "Codacy Security Scan"
check with:

  The CodeQL Action does not support uploading multiple SARIF runs
  with the same category. Please update your workflow to upload a
  single run per category.

Insert a jq post-processing step between the Codacy analysis and the
upload to stamp each run with a unique automationDetails.id
("codacy-run-0", "codacy-run-1", …). The expression is a no-op on
single-run SARIF files.

Ref: https://github.blog/changelog/2025-07-21-code-scanning-will-stop-combining-multiple-sarif-runs-uploaded-in-the-same-sarif-file/

github-advanced-security AI commented Jun 5, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

7 similar comments

github-advanced-security AI commented Jun 5, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

github-advanced-security AI commented Jun 5, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

github-advanced-security AI commented Jun 5, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

github-advanced-security AI commented Jun 5, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

github-advanced-security AI commented Jun 5, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

github-advanced-security AI commented Jun 5, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

github-advanced-security AI commented Jun 5, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

nathanaelytj disabled auto-merge

June 5, 2026 05:10

nathanaelytj merged commit a961ed4 into latest

9 checks passed

nathanaelytj deleted the fix/curl-symlink-guard branch

June 5, 2026 05:10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet