Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, alexellis/arkade-get@1eef818e467c387d3f50cfe0d2c565d1cbe82b03, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: alexellis/arkade-get@1eef818e467c387d3f50cfe0d2c565d1cbe82b03. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

embed field value must be shorter than 1024, got 1781 [`04e2509`](https://github.com/SimplicityGuy/discogsography/commit/04e2509f61607298d7f4af26ee345c778d59a371) fix(ci): stop hitting E2BIG in update-dependencies workflow (#310) * fix(ci): stop hitting E2BIG in update-dependencies workflow The weekly "Update Dependencies" job was failing with "Argument list too long" at both "Create Pull Request" (node) and "Summary" (bash) steps. The update script's full ~200KB output was being written to $GITHUB_OUTPUT and then interpolated into the PR body and a downstream env var, exceeding the OS E2BIG argv+envp limit when spawning those processes. Workflow changes: - Drop the `output<<ENDOFOUTPUT` block; stream the script's stdout via `tee update-output.txt` so it still shows up in the runner log and gets uploaded as the `update-logs` artifact. - Remove the `<details>Full update output</details>` block from the PR body (artifact link replaces it). - Remove `UPDATE_OUTPUT` env from the Summary step; tail the last 100 lines of the local file on failure if it still exists. - Install hadolint via arkade so the pre-commit hook invoked by `scripts/update-project.sh` doesn't fail with "Executable hadolint not found" (mirrors code-quality.yml). - Capture the update script's exit code past `tee` with ${PIPESTATUS[0]}. - Quote `exit "$EXIT_CODE"` to satisfy shellcheck SC2086. justfile change: - `update-uv` now tolerates managed installs (GitHub Actions runner image, pipx, brew) by recognising the "standalone installation scripts" error and exiting 0 with a skip message, eliminating the spurious error that appeared on every CI run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: update deps --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

embed field value must be shorter than 1024, got 1781 [`04e2509`](https://github.com/SimplicityGuy/discogsography/commit/04e2509f61607298d7f4af26ee345c778d59a371) fix(ci): stop hitting E2BIG in update-dependencies workflow (#310) * fix(ci): stop hitting E2BIG in update-dependencies workflow The weekly "Update Dependencies" job was failing with "Argument list too long" at both "Create Pull Request" (node) and "Summary" (bash) steps. The update script's full ~200KB output was being written to $GITHUB_OUTPUT and then interpolated into the PR body and a downstream env var, exceeding the OS E2BIG argv+envp limit when spawning those processes. Workflow changes: - Drop the `output<<ENDOFOUTPUT` block; stream the script's stdout via `tee update-output.txt` so it still shows up in the runner log and gets uploaded as the `update-logs` artifact. - Remove the `<details>Full update output</details>` block from the PR body (artifact link replaces it). - Remove `UPDATE_OUTPUT` env from the Summary step; tail the last 100 lines of the local file on failure if it still exists. - Install hadolint via arkade so the pre-commit hook invoked by `scripts/update-project.sh` doesn't fail with "Executable hadolint not found" (mirrors code-quality.yml). - Capture the update script's exit code past `tee` with ${PIPESTATUS[0]}. - Quote `exit "$EXIT_CODE"` to satisfy shellcheck SC2086. justfile change: - `update-uv` now tolerates managed installs (GitHub Actions runner image, pipx, brew) by recognising the "standalone installation scripts" error and exiting 0 with a skip message, eliminating the spurious error that appeared on every CI run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: update deps --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

embed field value must be shorter than 1024, got 1781 [`04e2509`](https://github.com/SimplicityGuy/discogsography/commit/04e2509f61607298d7f4af26ee345c778d59a371) fix(ci): stop hitting E2BIG in update-dependencies workflow (#310) * fix(ci): stop hitting E2BIG in update-dependencies workflow The weekly "Update Dependencies" job was failing with "Argument list too long" at both "Create Pull Request" (node) and "Summary" (bash) steps. The update script's full ~200KB output was being written to $GITHUB_OUTPUT and then interpolated into the PR body and a downstream env var, exceeding the OS E2BIG argv+envp limit when spawning those processes. Workflow changes: - Drop the `output<<ENDOFOUTPUT` block; stream the script's stdout via `tee update-output.txt` so it still shows up in the runner log and gets uploaded as the `update-logs` artifact. - Remove the `<details>Full update output</details>` block from the PR body (artifact link replaces it). - Remove `UPDATE_OUTPUT` env from the Summary step; tail the last 100 lines of the local file on failure if it still exists. - Install hadolint via arkade so the pre-commit hook invoked by `scripts/update-project.sh` doesn't fail with "Executable hadolint not found" (mirrors code-quality.yml). - Capture the update script's exit code past `tee` with ${PIPESTATUS[0]}. - Quote `exit "$EXIT_CODE"` to satisfy shellcheck SC2086. justfile change: - `update-uv` now tolerates managed installs (GitHub Actions runner image, pipx, brew) by recognising the "standalone installation scripts" error and exiting 0 with a skip message, eliminating the spurious error that appeared on every CI run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: update deps --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

embed field value must be shorter than 1024, got 1781 [`04e2509`](https://github.com/SimplicityGuy/discogsography/commit/04e2509f61607298d7f4af26ee345c778d59a371) fix(ci): stop hitting E2BIG in update-dependencies workflow (#310) * fix(ci): stop hitting E2BIG in update-dependencies workflow The weekly "Update Dependencies" job was failing with "Argument list too long" at both "Create Pull Request" (node) and "Summary" (bash) steps. The update script's full ~200KB output was being written to $GITHUB_OUTPUT and then interpolated into the PR body and a downstream env var, exceeding the OS E2BIG argv+envp limit when spawning those processes. Workflow changes: - Drop the `output<<ENDOFOUTPUT` block; stream the script's stdout via `tee update-output.txt` so it still shows up in the runner log and gets uploaded as the `update-logs` artifact. - Remove the `<details>Full update output</details>` block from the PR body (artifact link replaces it). - Remove `UPDATE_OUTPUT` env from the Summary step; tail the last 100 lines of the local file on failure if it still exists. - Install hadolint via arkade so the pre-commit hook invoked by `scripts/update-project.sh` doesn't fail with "Executable hadolint not found" (mirrors code-quality.yml). - Capture the update script's exit code past `tee` with ${PIPESTATUS[0]}. - Quote `exit "$EXIT_CODE"` to satisfy shellcheck SC2086. justfile change: - `update-uv` now tolerates managed installs (GitHub Actions runner image, pipx, brew) by recognising the "standalone installation scripts" error and exiting 0 with a skip message, eliminating the spurious error that appeared on every CI run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: update deps --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

embed field value must be shorter than 1024, got 1781 [`04e2509`](https://github.com/SimplicityGuy/discogsography/commit/04e2509f61607298d7f4af26ee345c778d59a371) fix(ci): stop hitting E2BIG in update-dependencies workflow (#310) * fix(ci): stop hitting E2BIG in update-dependencies workflow The weekly "Update Dependencies" job was failing with "Argument list too long" at both "Create Pull Request" (node) and "Summary" (bash) steps. The update script's full ~200KB output was being written to $GITHUB_OUTPUT and then interpolated into the PR body and a downstream env var, exceeding the OS E2BIG argv+envp limit when spawning those processes. Workflow changes: - Drop the `output<<ENDOFOUTPUT` block; stream the script's stdout via `tee update-output.txt` so it still shows up in the runner log and gets uploaded as the `update-logs` artifact. - Remove the `<details>Full update output</details>` block from the PR body (artifact link replaces it). - Remove `UPDATE_OUTPUT` env from the Summary step; tail the last 100 lines of the local file on failure if it still exists. - Install hadolint via arkade so the pre-commit hook invoked by `scripts/update-project.sh` doesn't fail with "Executable hadolint not found" (mirrors code-quality.yml). - Capture the update script's exit code past `tee` with ${PIPESTATUS[0]}. - Quote `exit "$EXIT_CODE"` to satisfy shellcheck SC2086. justfile change: - `update-uv` now tolerates managed installs (GitHub Actions runner image, pipx, brew) by recognising the "standalone installation scripts" error and exiting 0 with a skip message, eliminating the spurious error that appeared on every CI run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: update deps --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

embed field value must be shorter than 1024, got 1781 [`04e2509`](https://github.com/SimplicityGuy/discogsography/commit/04e2509f61607298d7f4af26ee345c778d59a371) fix(ci): stop hitting E2BIG in update-dependencies workflow (#310) * fix(ci): stop hitting E2BIG in update-dependencies workflow The weekly "Update Dependencies" job was failing with "Argument list too long" at both "Create Pull Request" (node) and "Summary" (bash) steps. The update script's full ~200KB output was being written to $GITHUB_OUTPUT and then interpolated into the PR body and a downstream env var, exceeding the OS E2BIG argv+envp limit when spawning those processes. Workflow changes: - Drop the `output<<ENDOFOUTPUT` block; stream the script's stdout via `tee update-output.txt` so it still shows up in the runner log and gets uploaded as the `update-logs` artifact. - Remove the `<details>Full update output</details>` block from the PR body (artifact link replaces it). - Remove `UPDATE_OUTPUT` env from the Summary step; tail the last 100 lines of the local file on failure if it still exists. - Install hadolint via arkade so the pre-commit hook invoked by `scripts/update-project.sh` doesn't fail with "Executable hadolint not found" (mirrors code-quality.yml). - Capture the update script's exit code past `tee` with ${PIPESTATUS[0]}. - Quote `exit "$EXIT_CODE"` to satisfy shellcheck SC2086. justfile change: - `update-uv` now tolerates managed installs (GitHub Actions runner image, pipx, brew) by recognising the "standalone installation scripts" error and exiting 0 with a skip message, eliminating the spurious error that appeared on every CI run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: update deps --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

embed field value must be shorter than 1024, got 1781 [`04e2509`](https://github.com/SimplicityGuy/discogsography/commit/04e2509f61607298d7f4af26ee345c778d59a371) fix(ci): stop hitting E2BIG in update-dependencies workflow (#310) * fix(ci): stop hitting E2BIG in update-dependencies workflow The weekly "Update Dependencies" job was failing with "Argument list too long" at both "Create Pull Request" (node) and "Summary" (bash) steps. The update script's full ~200KB output was being written to $GITHUB_OUTPUT and then interpolated into the PR body and a downstream env var, exceeding the OS E2BIG argv+envp limit when spawning those processes. Workflow changes: - Drop the `output<<ENDOFOUTPUT` block; stream the script's stdout via `tee update-output.txt` so it still shows up in the runner log and gets uploaded as the `update-logs` artifact. - Remove the `<details>Full update output</details>` block from the PR body (artifact link replaces it). - Remove `UPDATE_OUTPUT` env from the Summary step; tail the last 100 lines of the local file on failure if it still exists. - Install hadolint via arkade so the pre-commit hook invoked by `scripts/update-project.sh` doesn't fail with "Executable hadolint not found" (mirrors code-quality.yml). - Capture the update script's exit code past `tee` with ${PIPESTATUS[0]}. - Quote `exit "$EXIT_CODE"` to satisfy shellcheck SC2086. justfile change: - `update-uv` now tolerates managed installs (GitHub Actions runner image, pipx, brew) by recognising the "standalone installation scripts" error and exiting 0 with a skip message, eliminating the spurious error that appeared on every CI run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: update deps --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

embed field value must be shorter than 1024, got 1781 [`04e2509`](https://github.com/SimplicityGuy/discogsography/commit/04e2509f61607298d7f4af26ee345c778d59a371) fix(ci): stop hitting E2BIG in update-dependencies workflow (#310) * fix(ci): stop hitting E2BIG in update-dependencies workflow The weekly "Update Dependencies" job was failing with "Argument list too long" at both "Create Pull Request" (node) and "Summary" (bash) steps. The update script's full ~200KB output was being written to $GITHUB_OUTPUT and then interpolated into the PR body and a downstream env var, exceeding the OS E2BIG argv+envp limit when spawning those processes. Workflow changes: - Drop the `output<<ENDOFOUTPUT` block; stream the script's stdout via `tee update-output.txt` so it still shows up in the runner log and gets uploaded as the `update-logs` artifact. - Remove the `<details>Full update output</details>` block from the PR body (artifact link replaces it). - Remove `UPDATE_OUTPUT` env from the Summary step; tail the last 100 lines of the local file on failure if it still exists. - Install hadolint via arkade so the pre-commit hook invoked by `scripts/update-project.sh` doesn't fail with "Executable hadolint not found" (mirrors code-quality.yml). - Capture the update script's exit code past `tee` with ${PIPESTATUS[0]}. - Quote `exit "$EXIT_CODE"` to satisfy shellcheck SC2086. justfile change: - `update-uv` now tolerates managed installs (GitHub Actions runner image, pipx, brew) by recognising the "standalone installation scripts" error and exiting 0 with a skip message, eliminating the spurious error that appeared on every CI run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: update deps --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "POSTGRES_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "NEO4J_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

embed field value must be shorter than 1024, got 1781 [`04e2509`](https://github.com/SimplicityGuy/discogsography/commit/04e2509f61607298d7f4af26ee345c778d59a371) fix(ci): stop hitting E2BIG in update-dependencies workflow (#310) * fix(ci): stop hitting E2BIG in update-dependencies workflow The weekly "Update Dependencies" job was failing with "Argument list too long" at both "Create Pull Request" (node) and "Summary" (bash) steps. The update script's full ~200KB output was being written to $GITHUB_OUTPUT and then interpolated into the PR body and a downstream env var, exceeding the OS E2BIG argv+envp limit when spawning those processes. Workflow changes: - Drop the `output<<ENDOFOUTPUT` block; stream the script's stdout via `tee update-output.txt` so it still shows up in the runner log and gets uploaded as the `update-logs` artifact. - Remove the `<details>Full update output</details>` block from the PR body (artifact link replaces it). - Remove `UPDATE_OUTPUT` env from the Summary step; tail the last 100 lines of the local file on failure if it still exists. - Install hadolint via arkade so the pre-commit hook invoked by `scripts/update-project.sh` doesn't fail with "Executable hadolint not found" (mirrors code-quality.yml). - Capture the update script's exit code past `tee` with ${PIPESTATUS[0]}. - Quote `exit "$EXIT_CODE"` to satisfy shellcheck SC2086. justfile change: - `update-uv` now tolerates managed installs (GitHub Actions runner image, pipx, brew) by recognising the "standalone installation scripts" error and exiting 0 with a skip message, eliminating the spurious error that appeared on every CI run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: update deps --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "JWT_SECRET_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "POSTGRES_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

embed field value must be shorter than 1024, got 1781 [`04e2509`](https://github.com/SimplicityGuy/discogsography/commit/04e2509f61607298d7f4af26ee345c778d59a371) fix(ci): stop hitting E2BIG in update-dependencies workflow (#310) * fix(ci): stop hitting E2BIG in update-dependencies workflow The weekly "Update Dependencies" job was failing with "Argument list too long" at both "Create Pull Request" (node) and "Summary" (bash) steps. The update script's full ~200KB output was being written to $GITHUB_OUTPUT and then interpolated into the PR body and a downstream env var, exceeding the OS E2BIG argv+envp limit when spawning those processes. Workflow changes: - Drop the `output<<ENDOFOUTPUT` block; stream the script's stdout via `tee update-output.txt` so it still shows up in the runner log and gets uploaded as the `update-logs` artifact. - Remove the `<details>Full update output</details>` block from the PR body (artifact link replaces it). - Remove `UPDATE_OUTPUT` env from the Summary step; tail the last 100 lines of the local file on failure if it still exists. - Install hadolint via arkade so the pre-commit hook invoked by `scripts/update-project.sh` doesn't fail with "Executable hadolint not found" (mirrors code-quality.yml). - Capture the update script's exit code past `tee` with ${PIPESTATUS[0]}. - Quote `exit "$EXIT_CODE"` to satisfy shellcheck SC2086. justfile change: - `update-uv` now tolerates managed installs (GitHub Actions runner image, pipx, brew) by recognising the "standalone installation scripts" error and exiting 0 with a skip message, eliminating the spurious error that appeared on every CI run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: update deps --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Docker cache hit for brainzgraphinator

Service: brainzgraphinator, Duration: 127s, Cache Used: true

Docker cache hit for dashboard

Service: dashboard, Duration: 124s, Cache Used: true

Docker cache hit for brainztableinator

Service: brainztableinator, Duration: 139s, Cache Used: true

Docker cache hit for insights

Service: insights, Duration: 144s, Cache Used: true

Docker cache hit for tableinator

Service: tableinator, Duration: 161s, Cache Used: true

Docker cache hit for graphinator

Service: graphinator, Duration: 173s, Cache Used: true

Docker cache hit for explore

Service: explore, Duration: 182s, Cache Used: true

Docker cache hit for schema-init

Service: schema-init, Duration: 182s, Cache Used: true

Docker cache hit for api

Service: api, Duration: 177s, Cache Used: true

Docker cache hit for extractor