…868)

The release workflow introduced in #866 fails during binary compilation
with `directory not found` error. The build command references
`./cmd/oxia`, but the repository structure has the main package at
`./cmd`. Additionally, the workflow was missing important build flags
that are used in the Makefile.

## Changes

- **Fixed build path**: Updated from `./cmd/oxia` to `./cmd` to match
the repository structure
- **Created new Makefile target**: Added `release-build` target that
encapsulates all release build logic with parameters:
  - `OUTPUT_DIR`: Directory for build output
  - `OUTPUT_NAME`: Name of the output binary
  - `GOOS`: Target operating system
  - `GOARCH`: Target architecture
- **Parameter validation**: Added validation to the Makefile target to
ensure all required parameters are provided with helpful error messages
- **Updated workflow**: Changed the workflow to use `make release-build`
instead of direct `go build` commands

The `release-build` target includes the same build flags as the standard
`build` target:
- `-tags disable_trap`: Disables trap functionality for production
builds
- `-ldflags "-X main.version=${VERSION}"`: Embeds version information
into the binary
- `-v`: Enables verbose output
- Version extraction using `git describe --tags --always | cut -c2-`

```yaml
# Before
go build -o dist/oxia/bin/oxia${{ matrix.suffix }} ./cmd/oxia

# After  
make release-build \
  OUTPUT_DIR=dist/oxia \
  OUTPUT_NAME=oxia${{ matrix.suffix }} \
  GOOS=${{ matrix.goos }} \
  GOARCH=${{ matrix.goarch }}
```

## Benefits

- **Centralized build logic**: All build flags are maintained in the
Makefile, not duplicated in the workflow
- **Automatic updates**: Future changes to build flags will
automatically apply to the release workflow
- **Consistency**: Ensures local builds and CI builds use identical
configuration
- **Maintainability**: Single source of truth for build configuration
reduces maintenance burden

This enables the workflow to build cross-platform binaries
(linux/darwin/windows, amd64/arm64) successfully with proper version
information and build configuration that stays in sync with the
project's Makefile.

<!-- START COPILOT ORIGINAL PROMPT -->



<details>

<summary>Original prompt</summary>

> 
> ----
> 
> *This section details on the original issue you should resolve*
> 
> <issue_title>fixes: release workflow</issue_title>
> <issue_description>### Motivation 
> 
> #866 introduced a new release
workflow. please check the action and try to fix it.</issue_description>
> 
> ## Comments on the Issue (you are @copilot in this section)
> 
> <comments>
> </comments>
> 


</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes #867

<!-- START COPILOT CODING AGENT TIPS -->
---

✨ Let Copilot coding agent [set things up for
you](https://github.com/oxia-db/oxia/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot)
— coding agent works faster and does higher quality work when set up for
your repo.

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: mattisonchao <74767115+mattisonchao@users.noreply.github.com>