ci(native): Native Image workflow_dispatch stub (enables testing PR #5323)

[robfrank]

What does this PR do?

Adds a minimal workflow_dispatch stub of the Native Image workflow to main.

Motivation

The full Native Image workflow (on feat/native-image, PR #5323) triggers only on workflow_dispatch and release, so it cannot be exercised from a PR. GitHub only registers a workflow as dispatchable once a workflow of that name exists on the default branch; dispatching then runs the version of the file present on the selected ref.

Merging this stub lets the full workflow be run against feat/native-image (select that branch in "Run workflow") to validate the real 5-target build, smoke, and Docker logic before merge. Dispatch is safe: in the full workflow, Docker pushes are gated to the release event, so a workflow_dispatch run builds and smoke-tests (--load + local container smoke) without publishing anything to arcadedata/arcadedb.

Related issues

Bootstraps testing for PR #5323 (experimental GraalVM native-image build). This stub is replaced by the real workflow when that feature merges.

Additional Notes

The stub does nothing but a checkout + an echo. After it merges, feat/native-image will be rebased onto main (a trivial one-file conflict on native-image.yml, resolved in favor of the feature branch's full version).

Checklist

• I have run the build using mvn clean package command (n/a - workflow-only change; actionlint + YAML validation pass)
• My unit tests cover both failure and success scenarios (n/a - stub workflow, no logic)

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Coverage ∅ diff coverage · -6.95% coverage variation

Metric	Results
Coverage variation	✅ -6.95% coverage variation
Diff coverage	✅ ∅ diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (99d62c2)	140670	104850	74.54%
Head commit (d96e983)	172571 (+31901)	116634 (+11784)	67.59% (-6.95%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#5324)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[claude]

Code Review

Reviewed the single-file change (.github/workflows/native-image.yml). This is a clean, minimal, low-risk stub, and the motivation is well documented both in the PR description and inline in the workflow comment. Nice touch pinning actions/checkout to a full commit SHA (9c091bb... = v7.0.0), which matches the SHA already used elsewhere in the repo and satisfies the SHA-pinning convention.

Suggestions (non-blocking)

1. Add a least-privilege permissions block. This is the only workflow in .github/workflows/ that does not declare a permissions block - every other workflow does. Without an explicit block, the job inherits the repository/organization default GITHUB_TOKEN permissions, which may be broader than needed. Since the stub only does a checkout + echo, it needs nothing: adding a top-level permissions: {} (or contents: read) keeps the stub consistent with the rest of the repo and follows least privilege for the short time it lives on main.

2. Minor: the checkout step is unnecessary for a pure echo. The stub run: echo ... does not use the repository contents, so the actions/checkout step could be dropped entirely to make the stub even more minimal. Not important given the file is transient, but it would remove the only step that touches the token/filesystem.

Notes

• The reasoning that a workflow_dispatch-only workflow must exist on the default branch before it becomes dispatchable, and that dispatch then executes the file from the selected ref, is correct - this is the right mechanism to unblock testing PR 5323.
• The plan to replace this stub with the full workflow on merge of feat/native-image (resolving the one-file conflict in favor of the feature branch) is sound. Worth confirming the follow-up actually lands so a bare echo stub does not linger on main.
• No security, performance, or correctness concerns. Test coverage is n/a for a workflow-only stub, as noted in the checklist.

Overall: LGTM. The permissions block addition is the only thing I would recommend before merge.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.63%. Comparing base (99d62c2) to head (d96e983).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #5324      +/-   ##
============================================
+ Coverage     65.62%   65.63%   +0.01%     
- Complexity      992      996       +4     
============================================
  Files          1716     1716              
  Lines        140670   140670              
  Branches      30119    30119              
============================================
+ Hits          92315    92332      +17     
+ Misses        35861    35851      -10     
+ Partials      12494    12487       -7     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.