Skip to content

v0.7.3: jira oauth scope fix, read-replica client, table wire data fix, db migrations from ci, docs updates, read replicas #18677

v0.7.3: jira oauth scope fix, read-replica client, table wire data fix, db migrations from ci, docs updates, read replicas

v0.7.3: jira oauth scope fix, read-replica client, table wire data fix, db migrations from ci, docs updates, read replicas #18677

Triggered via pull request June 11, 2026 01:57
@Sg312Sg312
synchronize #4959
staging
Status Success
Total duration 6m 12s
Artifacts

ci.yml

on: pull_request
Detect Version
0s
Detect Version
Test and Build  /  Test and Build
6m 2s
Test and Build / Test and Build
Migrate Dev DB  /  Apply Database Migrations
Migrate Dev DB / Apply Database Migrations
Check Docs Changes
0s
Check Docs Changes
Matrix: Build ARM64 (GHCR Only)
Migrate DB  /  Apply Database Migrations
Migrate DB / Apply Database Migrations
Matrix: Build Dev ECR
Matrix: Build AMD64
Matrix: Create GHCR Manifests
Process Docs  /  Process Documentation Embeddings
Process Docs / Process Documentation Embeddings
Create GitHub Release
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Test and Build / Test and Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/