Skip to content

Restoration plan (when ready to release) #86

Description

@cnicholas
│ Wheel building  │ only on vX.Y.Z tag (publish.yml) │ unchanged                                              │
└─────────────────┴──────────────────────────────────┴────────────────────────────────────────────────────────┘

Restoration plan (when ready to release)

Before tagging 0.1.0:
1. Restore the full matrix in ci.yml (revert this issue's commit).
2. Push and verify all 9 jobs go green on the actual matrix, not just ubuntu/3.11.
3. Then tag v0.1.0.

Process convention (no code)

Until restoration: 
- Batch related commits locally and push as a single set instead of one-push-per-commit.
- Use [skip ci] in commit messages for docs-only or planning commits.

Invariants to preserve

- Coverage gate (fail_under = 80) still enforced on the single job.
- Mypy + lint still enforced on the single job.
- Nothing changes for publish.yml.

Verification

- Push a trivial change after applying; confirm only 1 job runs in the Actions tab.
- Manually verify locally before relying on CI: pytest tests/, mypy processbehavior/, ruff check.

Related

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions