Skip to content

ci: run production publish job in the production environment - #211

Open
DeepakSingh80 wants to merge 1 commit into
developmentfrom
chore/production-environment
Open

DeepakSingh80 wants to merge 1 commit into
developmentfrom
chore/production-environment

Conversation

@DeepakSingh80

Copy link
Copy Markdown

What

Adds environment: production to the production publish job in .github/workflows/publish.yml (job build).

Why

Native SDK CI/CD Phase 1 §4: production publishing runs only through a production GitHub Environment pinned to the production branch, following the gw-fe-las pattern (branch policy, no required reviewers).

Before merging

  • A repo admin has created the production Environment: Settings → Environments → production → Deployment branches → Selected branches → production; no required reviewers. If this merges first, GitHub auto-creates the Environment without the branch policy.
  • Production releases are cut from the production branch. With the policy in place, this job will no longer run when dispatched from prod / master.

No secrets move: this job uses OIDC (no stored secrets).

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant