Align module release documentation with implemented behavior
This commit is contained in:
@@ -22,10 +22,12 @@ declared module stored at `integrations/core` derives the same tag. ReleaseKit
|
||||
removes a final physical `/v2` directory from the tag prefix only when the
|
||||
module declaration has that `/v2` suffix. A module-local note stays at
|
||||
`<module>/docs/releases/<version>.md`, including a physical `/v2` directory.
|
||||
Shared license files remain at the repository root. Use the complete derived
|
||||
tag as the immutable source ref in note links, with paths rooted at the
|
||||
repository; license footer links target the root `COPYRIGHT`, `LICENSE`, and
|
||||
`docs/oss/attribution.md` files. The client first reads
|
||||
The default shared validation convention uses repository-root `COPYRIGHT`,
|
||||
`LICENSE`, and `docs/oss/attribution.md` when present. Consumers own their license
|
||||
layout and release-note links. Use the complete derived tag as the immutable
|
||||
source ref and the actual repository-relative file paths in those links.
|
||||
Shared-file selection controls validation inputs; delivery preserves the
|
||||
committed note and its footer links. The client first reads
|
||||
`/api/v1/repos/{owner}/{repo}/tags/{tag}` and requires the hosted tag's commit
|
||||
SHA to equal the captured source commit. It then reads
|
||||
`/api/v1/repos/{owner}/{repo}/releases/tags/{tag}`. A matching existing page
|
||||
|
||||
Reference in New Issue
Block a user