Skip to content

Application update scheduler #7831

Application update scheduler

Application update scheduler #7831

Triggered via schedule April 18, 2026 10:21
Status Failure
Total duration 9m 27s
Artifacts 4

update-scheduler.yml

on: schedule
Get Configuration
6s
Get Configuration
Matrix: update-branches
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 7 warnings, and 39 notices
Update R1-2025-ci / Update Application / Commit Changes / Commit and Push Changes
Process completed with exit code 1.
Update R1-2025-ci / Update Application / Commit Changes / Commit and Push Changes
Failed to push changes to 'version-update/R1-2025-ci'
Update snapshot / Update Application / Update Application
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/
Update snapshot / Update Application / Upload Results
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/
Update R1-2025-ci / Update Application / Update Application
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/
Update R1-2025-ci / Update Application / Commit Changes / Commit and Push Changes
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/
Update R1-2025-ci / Update Application / Manage Pull Request
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/
Update R1-2025-ci / Update Application / Upload Results
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/
Update R1-2025-ci / Send Notifications
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/
Get Configuration
Configuration parsed:
Get Configuration
Branch exists and is enabled: snapshot
Get Configuration
Checking branch: snapshot
Get Configuration
Branch exists and is enabled: R1-2025-ci
Get Configuration
Checking branch: R1-2025-ci
Get Configuration
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"}]}
Get Configuration
Has explicit ruleset config: true
Get Configuration
Parsing configuration from /tmp/update-config.yml
Get Configuration
Configuration file exists
Get Configuration
Checking for configuration file: .github/update-config.yml in folio-org/app-platform-complete on branch master
Update R1-2025-ci / Update Application / Prepare Update Context
Update branch version-update/R1-2025-ci not found, will operate on R1-2025-ci and create branch on commit
Update snapshot / Update Application / Update Application
No changes detected
Update snapshot / Update Application / Update Application
Maven execution completed successfully
Update snapshot / Update Application / Update Application
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=100200000007831 -DuseProjectVersion=true -DnoVersionBump=true
Update snapshot / Update Application / Update Application
Running update mode
Update snapshot / Update Application / Update Application
All module versions are valid semver/semver range
Update snapshot / Update Application / Update Application
Validating module versions in application.template.json
Update R1-2025-ci / Update Application / Update Application
Including pom.xml in state file artifact (version was bumped)
Update R1-2025-ci / Update Application / Update Application
Total module changes: 26
Update R1-2025-ci / Update Application / Update Application
Application descriptor generated: app-platform-complete-2.5.6.json (category: NONE)
Update R1-2025-ci / Update Application / Update Application
Maven execution completed successfully
Update R1-2025-ci / Update Application / Update Application
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=7831 -DuseProjectVersion=true -DnoVersionBump=true
Update R1-2025-ci / Update Application / Update Application
All module versions are valid semver/semver range
Update R1-2025-ci / Update Application / Update Application
Validating module versions in application.template.json
Update R1-2025-ci / Update Application / Update Application
Version bumped: 2.5.5 -> 2.5.6
Update R1-2025-ci / Update Application / Commit Changes / Commit and Push Changes
Pushing changes to branch 'version-update/R1-2025-ci'
Update R1-2025-ci / Update Application / Commit Changes / Commit and Push Changes
Successfully committed changes: 36b30ffe378e86fd428c76f9a29834c430bc2a1a
Update R1-2025-ci / Update Application / Commit Changes / Commit and Push Changes
Successfully switched to branch 'version-update/R1-2025-ci'
Update R1-2025-ci / Update Application / Commit Changes / Commit and Push Changes
Creating new branch 'version-update/R1-2025-ci'
Update R1-2025-ci / Update Application / Commit Changes / Commit and Push Changes
Switching to branch 'version-update/R1-2025-ci' (from source 'R1-2025-ci')
Update R1-2025-ci / Update Application / Commit Changes / Commit and Push Changes
Git configured for automated commits
Update R1-2025-ci / Update Application / Manage Pull Request
Checking for existing PR from version-update/R1-2025-ci to R1-2025-ci
Update R1-2025-ci / Update Application / Manage Pull Request
Found 26 module updates
Update R1-2025-ci / Update Application / Manage Pull Request
Comparing application versions

Artifacts

Produced during runtime
Name Size Digest
app-platform-complete-R1-2025-ci-descriptor Expired
88.4 KB
sha256:4de2c13399afe0328c0bce3fcb76fa5f8842fa5a38826aed6b79624be6b44594
app-platform-complete-R1-2025-ci-state-file Expired
89.3 KB
sha256:64223ed4a21f937fbf94d47749b7053e4abe9bc2691e47b59fc0284be8abe4eb
result-app-platform-complete-R1-2025-ci Expired
840 Bytes
sha256:1135eed0b5b37194c9e2bf60e3f2dbb663bc190f708d3a6a51168541db0e60cf
result-app-platform-complete-snapshot Expired
421 Bytes
sha256:950a41db6354b56b3e9cde5af3b6dc0a8ce24ad66b44a61e89c1fc20bf480e01