fix: pass X-GitHub-Api-Version as top-level header in dispatchWorkflow

[Copilot]

dispatchWorkflow was nesting the API version header under request.headers, which @octokit/request carries through the params object but never applies to the actual HTTP request — only top-level headers are sent over the wire. This caused the deprecation warning in the "Route slash command" CI step.

Changes

• route_slash_command.cjs — move X-GitHub-Api-Version from request: { headers: {...} } to top-level headers: {...} in createWorkflowDispatch call
• route_slash_command.test.cjs — assert headers["X-GitHub-Api-Version"] instead of request.headers["X-GitHub-Api-Version"]

// before
await github.rest.actions.createWorkflowDispatch({
  ...,
  request: { headers: { "X-GitHub-Api-Version": GITHUB_API_VERSION } },
});

// after
await github.rest.actions.createWorkflowDispatch({
  ...,
  headers: { "X-GitHub-Api-Version": GITHUB_API_VERSION },
});

[Copilot]

Pull request overview

Fixes workflow dispatch requests so the X-GitHub-Api-Version header is sent as an actual HTTP header (top-level headers) rather than being nested under request.headers, which was not applied by the underlying request layer—eliminating the REST API deprecation warning seen in CI.

Changes:

• Move X-GitHub-Api-Version to the top-level headers option in github.rest.actions.createWorkflowDispatch.
• Update the unit test to assert against params.headers["X-GitHub-Api-Version"].

Show a summary per file

File	Description
actions/setup/js/route_slash_command.cjs	Sends X-GitHub-Api-Version via top-level headers in createWorkflowDispatch so it is applied to the HTTP request.
actions/setup/js/route_slash_command.test.cjs	Updates the assertion to match the corrected parameter shape (headers instead of request.headers).

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0