Skip to content

chore(pylon): disable inherited upstream workflows - #6

Merged
rynfar merged 1 commit into
pylonfrom
chore/pylon-workflow-boundaries
Aug 29, 2026
Merged

chore(pylon): disable inherited upstream workflows#6
rynfar merged 1 commit into
pylonfrom
chore/pylon-workflow-boundaries

Conversation

@rynfar

@rynfar rynfar commented Aug 29, 2026

Copy link
Copy Markdown

Problem

The Pylon product branch still carried Prime's Linear ticket gate and release publication workflow even though Pylon tracks work in GitHub issues and has not defined fork release ownership. Mirrored upstream automation must not become Pylon policy by inheritance.

Resolution

  • Remove the Linear ticket workflow from pylon.
  • Remove the inherited binary/package release workflow from pylon while release naming, provenance, signing, storage, and channels remain undefined.
  • Record the workflows explicitly retained after audit.
  • Document the singleton-safe branch policy: PRs, strict checks, conversation resolution, and admin enforcement with zero formal approvals until a second eligible reviewer exists.
  • Record the intentional omissions so future upstream merges preserve them.

The exact upstream mirror on main remains unchanged.

Validation

  • npm run check
  • git diff --check
  • Repository release secrets, variables, environments, and releases are empty
  • Independent operations and release audits found no blocker in the workflow deletions

Refs #1

Model: OpenAI Codex GPT-5.6
Harness: Prime Agent

Keep Prime Linear gating and release publication automation out of the Pylon product branch until Pylon owns those policies.
@rynfar
rynfar force-pushed the chore/pylon-workflow-boundaries branch from 804bfaf to 843891d Compare August 29, 2026 02:01
@rynfar

rynfar commented Aug 29, 2026

Copy link
Copy Markdown
Author

The first hosted run was not merged: Test (coding-agent 1/3) reported a Vitest environment-teardown import race after all 1,453 tests in the shard had passed. The PR changes only workflow/docs policy and do not touch the cited highlighter or test code. Rerunning the failed job and aggregate check; merge remains gated on a clean rerun.

@rynfar
rynfar merged commit 187f5f4 into pylon Aug 29, 2026
24 of 26 checks passed
@rynfar
rynfar deleted the chore/pylon-workflow-boundaries branch August 29, 2026 02:51
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