This repository ships from main through reviewed pull requests. The process below keeps releases incremental and contributor-friendly.
- Create a focused branch from
main. - Implement one bounded issue or a tightly-coupled batch.
- Run the relevant checks for the touched surfaces.
- Open a pull request with testing notes and rollout notes.
- Merge only when the branch is green and reviewer feedback is resolved.
Every pull request should call out:
- affected packages
- new or changed environment variables
- operational steps such as seeds, migrations, or infrastructure changes
- user-facing behavior changes
- Use conventional, human-readable commit messages for contributor clarity.
- Aggregate release notes by milestone or deployment window.
- Treat incompatible environment or deployment changes as release blockers until documented.
- No direct secret values in source control.
- No undocumented config changes.
- No silent changes to public API shapes or shared contracts.
- No unreviewed changes to payment or authentication flows.