Skip to content

Update codegen files - #95

Merged
ptr727-codegen[bot] merged 1 commit into
developfrom
codegen-develop
Jun 1, 2026
Merged

Update codegen files#95
ptr727-codegen[bot] merged 1 commit into
developfrom
codegen-develop

Conversation

@ptr727-codegen

Copy link
Copy Markdown
Contributor

This PR updates the codegen files.

@ptr727-codegen
ptr727-codegenBot enabled auto-merge (squash) June 1, 2026 03:02
@ptr727-codegen
ptr727-codegenBot merged commit ad39ee1 into developJun 1, 2026
22 checks passed
ptr727 added a commit that referenced this pull request Jun 4, 2026
Release merge of `develop` into `main`.
## Headline change (#98, closes#97)
Two-phase CI/CD that decouples merging from publishing across all four
delivery targets (Docker, NuGet, PyPI, console executable):
- **PRs smoke-test only** — path-gated, reduced builds (Docker
`linux/amd64`, trimmed executable matrix), no publish.
- **Sole publisher** — `publish-release.yml` (weekly schedule + manual
dispatch) builds/publishes **both** branches via a matrix; the `push`
trigger publishes only when the **`PUBLISH_ON_MERGE`** repository
variable is `true` (opt-in legacy continuous-release). Default is
two-phase.
- Parameterized chain (`ref`/`branch`/`smoke`, per-target `enable_*`
gates), branch-suffixed artifacts, branch-scoped Docker cache, hardened
required-status aggregator.
- Robustness: skip GitHub release on a duplicate version (no-op weeks),
pin the release tag to NBGV `GitCommitId`, global publish concurrency,
`cache-to`/login gating reviewed.
- CodeGen weekly → daily; `test-release-task.yml` +
`publish-periodic-docker-release.yml` removed.
- Corrected the Copilot review runbook (reliable `requestReviews`
mutation) and made the wait-for-maintainer-merge gate explicit.
Also includes routine codegen updates (#93, #95).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign up for freeto 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.

0 participants