Align release references and define clean tagging policy.
Remove stale links to deleted docs, document forward tagging conventions for repo/fork/version namespaces, and keep release checklist aligned with current workflow. Made-with: Cursor
This commit is contained in:
@@ -12,7 +12,7 @@ assignees: []
|
||||
- [ ] Core workflows smoke-tested
|
||||
- [ ] `forks/forks_manifest.yaml` reviewed/updated
|
||||
- [ ] `CHANGELOG.md` updated
|
||||
- [ ] Release notes drafted (`docs/RELEASE_NOTES_TEMPLATE.md`)
|
||||
- [ ] Release notes drafted (PR body + `CHANGELOG.md`)
|
||||
|
||||
## Publish
|
||||
|
||||
|
||||
+1
-3
@@ -8,15 +8,13 @@ The format is inspired by Keep a Changelog and SemVer.
|
||||
|
||||
### Added
|
||||
- Initial release/process scaffolding:
|
||||
- `docs/RELEASE_WORKFLOW.md`
|
||||
- `docs/REPO_AUDIT_2026-02-14.md`
|
||||
- release/versioning notes in repository docs
|
||||
- `forks/THIRD_PARTY.md`
|
||||
- `forks/forks_manifest.yaml`
|
||||
- `tools/report_mods.py`
|
||||
- Contribution/release templates:
|
||||
- `.github/PULL_REQUEST_TEMPLATE.md`
|
||||
- `.github/ISSUE_TEMPLATE/release_checklist.md`
|
||||
- `docs/RELEASE_NOTES_TEMPLATE.md`
|
||||
- RunPod_Comfy scaffold was previously added during iteration and has since been moved to a private management repository.
|
||||
|
||||
## [0.1.0] - 2026-02-14
|
||||
|
||||
@@ -33,11 +33,20 @@ RunPod management has been moved to a separate private repository for active ope
|
||||
|
||||
For production usage, install a pinned stable tag/commit instead of following moving branch heads.
|
||||
|
||||
- Release workflow: `docs/RELEASE_WORKFLOW.md`
|
||||
- Release workflow: `forks/README.md`
|
||||
- Change history: `CHANGELOG.md`
|
||||
- Fork tracking: `forks/THIRD_PARTY.md`, `forks/forks_manifest.yaml`
|
||||
- Fork workflow guide: `forks/README.md`
|
||||
|
||||
### Tagging Policy (from now on)
|
||||
|
||||
- Repo releases: `vMAJOR.MINOR.PATCH` (example: `v0.2.0`).
|
||||
- Fork code versions in paths use underscore format: `v1_0_1`, `v2_3_3`.
|
||||
- Comfy node ID namespace suffixes match fork version paths: `__koolook_v1_0_1`.
|
||||
- External raw checkout naming:
|
||||
- pinned: `<repo>-v<version>-koolook`
|
||||
- rolling upstream: `<repo>-main-upstream`
|
||||
|
||||
## External Fork Workflow (No Vendoring in MAIN)
|
||||
|
||||
This repository is the MAIN control repo. Large third-party repositories must stay outside MAIN.
|
||||
|
||||
@@ -38,6 +38,15 @@ For each fork entry in `forks/forks_manifest.yaml`:
|
||||
- `external_checkout.upstream_tracking_path_from_forks_root` = rolling upstream folder
|
||||
- `local_paths` = files tracked in MAIN
|
||||
|
||||
## Tagging Policy (from now on)
|
||||
|
||||
- MAIN repo tags use SemVer: `vMAJOR.MINOR.PATCH`.
|
||||
- Local fork version folders use underscore variant of the same version:
|
||||
- `v1_0_1`, `v2_3_3`, etc.
|
||||
- Node mapping namespace suffixes must match folder versions:
|
||||
- `__koolook_v1_0_1`, `__koolook_v2_3_3`, etc.
|
||||
- Keep `source_ref` + `pinned_commit` in `forks/forks_manifest.yaml` and `UPSTREAM_PIN.yaml`.
|
||||
|
||||
## Upgrade Flow Example (Radiance)
|
||||
|
||||
1. Compare current local version (`forks/radiance_koolook/versions/v1_0_1`) with pinned raw baseline (`../ComfyUI-Forks/radiance-v1.0.1-koolook`).
|
||||
|
||||
Reference in New Issue
Block a user