Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/download-artifact@v4. 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/checkout@v4, actions/create-github-app-token@v1, actions/download-artifact@v4. 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/upload-artifact@v4. 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: slackapi/slack-github-action@v2.1.1. 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/checkout@v4. 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/create-github-app-token@v1. 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/upload-artifact@v4. 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/

Configuration parsed:

Branch exists and is enabled: snapshot

Checking branch: snapshot

Branch exists and is enabled: R1-2025-ci

Checking branch: R1-2025-ci

Global ruleset config: {"enabled":true,"pattern":"{0}-eureka-ci","required_checks":[{"context":"eureka-ci / validate-application"}],"merge_queue":{"enabled":true,"check_response_timeout_minutes":60,"grouping_strategy":"ALLGREEN","max_entries_to_build":5,"max_entries_to_merge":5,"merge_method":"SQUASH","min_entries_to_merge":1,"min_entries_to_merge_wait_minutes":5},"bypass_actors":[{"actor_type":"Integration","bypass_mode":"always"}]}

Has explicit ruleset config: true

Parsing configuration from /tmp/update-config.yml

Configuration file exists

Checking for configuration file: .github/update-config.yml in folio-org/app-platform-complete on branch master

Found existing PR #59: https://github.com/folio-org/app-platform-complete/pull/59

Checking for existing PR from version-update/R1-2025-ci to R1-2025-ci

Update branch exists: version-update/R1-2025-ci

Total module changes: 2

Application descriptor generated: app-platform-complete-3.3.0-SNAPSHOT.100200000007961.json (category: NONE)

Maven execution completed successfully

Full Maven command: mvn -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn clean org.folio:folio-application-generator:1.4.0-SNAPSHOT:updateFromTemplate -U -e -DappDescriptorPath=application.lock.json -DtemplatePath=application.template.json -DvalidateArtifacts=true -DbuildNumber=100200000007961 -DuseProjectVersion=true -DnoVersionBump=true

Running update mode

All module versions are valid semver/semver range

Validating module versions in application.template.json

Application descriptor published successfully to https://far.ci.folio.org/applications/app-platform-complete-3.3.0-SNAPSHOT.100200000007961?full=true

Publishing application descriptor to FAR

Fetched app-consortia-manager

Fetched app-consortia

Fetched app-bulk-edit

Fetched app-authority-records

Fetched app-agreements

Fetched app-acquisitions

Fetched app-platform-minimal

Found 39 applications in platform descriptor

Platform descriptor loaded successfully from /tmp/tmp.JJAeDuPG8N/platform-descriptor.json

Fetch application descriptors from FAR for validation

Platform descriptor fetched successfully to /tmp/tmp.JJAeDuPG8N/platform-descriptor.json

Fetching platform descriptor from platform-lsp branch: snapshot

Successfully pushed changes to 'snapshot'

Pushing changes to branch 'snapshot'

Successfully committed changes: 241f4596313f813cdb55f8a0f48d473bd4603312

Successfully switched to branch 'snapshot'

Switching to existing branch 'snapshot'

Switching to branch 'snapshot' (from source 'snapshot')

Git configured for automated commits

Repository: app-platform-complete

Owner: folio-org

No changes detected

Maven execution completed successfully

Full Maven command: mvn -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn clean org.folio:folio-application-generator:1.4.0-SNAPSHOT:updateFromTemplate -U -e -DappDescriptorPath=application.lock.json -DtemplatePath=application.template.json -DvalidateArtifacts=true -DbuildNumber=7961 -DuseProjectVersion=true -DnoVersionBump=true

Running update mode

All module versions are valid semver/semver range

Validating module versions in application.template.json

Template file sourced from base branch

Fetching template from base branch: R1-2025-ci

Updated modules:

Found 27 module updates