Repository navigation
Own the template's .NET validation and publication workflows #534
Description
🤖 Generated by the Agentic Engineer
User story
As a .NET template adopter, I want product-specific build and publication workflows in this repository, so I can understand and maintain the complete pipeline without depending on unused shared exports.
The 2026-10-21 workflow census found one production consumer of the centralized .NET publisher and one effective consumer of centralized .NET validation. Catalogue fixture calls do not establish production reuse. This implements the maintainer's requested workflow ownership convention; generic actions and workflows with demonstrated reuse remain shared.
Acceptance criteria
- Move the single-consumer publisher into the existing local publication workflow without changing credential scope, pinned tools or release behavior.
- Deliver a repository-owned validation workflow preserving the Ubuntu, Windows and macOS build/test matrix and credential-free pull-request behavior.
- Preserve the existing protected validation until a reviewed declarative source cutover is deployed and verified; source preparation alone is not completion.
- Update contributor-facing and agent guidance to match the actual final pipeline.
- Verify exact-head CI and review, protected merge and post-merge enforcement before closing.
Outcome: clearer ownership and a self-contained scaffold, with no reduction in required validation. End-to-end effort includes provider-side source cutover and hosted matrix verification. Parent: #218.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Projects
- Status
Activity
chore: agent-claim #534 nonce=da0c7952254ddadf7024cc66d62aa630
chore: agent-claim #534 nonce=6e4b15dd65bf7fd6f41f39034064ddb5
devantler commentedon Oct 21, 2026
The repository-owned source migration is merged in #535. Catalogue PR #687 now finishes its unused shared-publisher cleanup. The old organization-required validation remains active; this issue stays open until repository-scoped enforcement is deployed and verified and that temporary organization rule is retired.
chore: agent-claim #534 nonce=6a8209560b3927bb75846512a77c825c
devantler commentedon Oct 21, 2026
Repository-specific enforcement is now prepared in organization configuration PR #688. It requires all three local platform checks and deliberately retains the original organization rule during rollout. Local regression and baseline validation passed; hosted CI, current-head review, protected merge and native enforcement verification remain outstanding.
The other continuation is #687, which removes the unused shared publisher after the native source migration merged in #535. Both continuations remain drafts while hosted checks are pending. Source preparation is not the completed enforcement cutover, so this issue remains open.
chore: agent-claim #534 nonce=67a0d2afa6b7b8c3aed8054e2a54c113
chore: agent-claim #534 nonce=b4c10eaa56eaa824e00943ce708ec9bd
chore: agent-claim #534 nonce=033ac1edc5417c1d9aaea2d75d12adfb