Skip to content

fix: regenerate code for CharSequence, fix nested proto package names #7

fix: regenerate code for CharSequence, fix nested proto package names

fix: regenerate code for CharSequence, fix nested proto package names #7

Triggered via push March 22, 2026 03:58
Status Failure
Total duration 2m 32s
Artifacts

release.yml

on: push
Matrix: Build release artifacts
Create GitHub release
0s
Create GitHub release
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
Build release artifacts (arm64)
Process completed with exit code 2.
Build release artifacts (arm64): cmd/jniservice/server.go#L239
assignment mismatch: 1 variable but app.ContextFromObject returns 2 values
Build release artifacts (amd64)
The strategy configuration was canceled because "build.arm64" failed
Build release artifacts (amd64)
Process completed with exit code 2.
Build release artifacts (amd64): cmd/jniservice/server.go#L239
assignment mismatch: 1 variable but app.ContextFromObject returns 2 values
Build release artifacts (arm64)
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/setup-go@v5, actions/setup-java@v4, android-actions/setup-android@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build release artifacts (amd64)
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/setup-go@v5, actions/setup-java@v4, android-actions/setup-android@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/