fix(release): drop dangling docs artifacts and enforce manifest schema - #21
Merged
Merged
Conversation
PR #18 removed the documentation packaging steps but left the release notes advertising a docs snapshot tarball and the GitHub release step looking for it. Nothing writes dist/docs, so the published notes point customers at an artifact that is never produced. Extend docs.sourceFormat with the values the manifests actually use. The docs pipeline moved to static-site and the schema was never updated, so v1.0.2 and v1.1.0 did not conform. Add snapshotTag, which the release tooling already emits. Validate every release manifest against the schema in helm CI. The schema was unreferenced, which is how the enum drifted unnoticed; helm-ci already triggers on schemas/**. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #18 removed the documentation packaging steps but left the release notes advertising a docs snapshot tarball and the GitHub release step looking for it. Nothing writes dist/docs, so the published notes point customers at an artifact that is never produced.
Extend docs.sourceFormat with the values the manifests actually use. The docs pipeline moved to static-site and the schema was never updated, so v1.0.2 and v1.1.0 did not conform. Add snapshotTag, which the release tooling already emits.
Validate every release manifest against the schema in helm CI. The schema was unreferenced, which is how the enum drifted unnoticed; helm-ci already triggers on schemas/**.