feat(hexclave): PR 2 — visible rebrand (Hexclave brand goes public) #6929
BilalG1db-migration-backwards-compatibility.yaml
on: pull_request
Check if migrations changed
9s
Back-compat — Current branch migrations with dev branch code
17m 35s
No migration changes (skipped)
0s
Forward-compat — Current branch code with ${{ needs.check-migrations-changed.outputs.base_branch }} branch migrations
0s
Annotations
3 errors and 1 warning
|
Back-compat — Current branch migrations with dev branch code
Canceling since a higher priority waiting request for DB migration compat-refs/pull/1481/merge exists
|
|
Back-compat — Current branch migrations with dev branch code
The operation was canceled.
|
|
DB migration compat
Canceling since a higher priority waiting request for DB migration compat-refs/pull/1481/merge exists
|
|
Back-compat — Current branch migrations with dev branch code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JarvusInnovations/background-action@2428e7b970a846423095c79d43f759abf979a635, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|