chore: remove production environment from build job in publish.yml

[ammodev]

No description provided.

[Copilot]

Pull request overview

Removes the production GitHub Environment association from the build job in the release publishing workflow.

Changes:

• Dropped environment: production from .github/workflows/publish.yml’s build job.

[Copilot]

Removing environment: production also removes GitHub Environment protections for this publishing job (e.g., required reviewers/approvals, environment-scoped secrets, and protection rules). If those safeguards are still desired for releases on version/*, keep the environment on the job or replace it with an equivalent gating mechanism (separate protected job, manual approval, etc.).

Suggested change

	build:
	build:
	environment: production

[Copilot]

publish.yml doesn’t declare explicit permissions for the GITHUB_TOKEN. Other workflows in this repo do (e.g. .github/workflows/api-dump-version.yml:7-10). Since this workflow creates a GitHub Release, define minimal required permissions at the workflow or job level (at least contents: write) to avoid relying on repository defaults and to keep token scope least-privilege.

Suggested change

	runs-on: ubuntu-latest
	runs-on: ubuntu-latest
	permissions:
	contents: write