Repository navigation
feat(release): automate API changelogs and release preparation - #2
Merged
Merged
Conversation
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
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.
Add independent API versioning, changelog generation and GitHub Releases using the same PR-first, tag-based process as the frontend. Release Please updates version.txt and the manifest; its bot PRs explicitly dispatch CI, including the empty-output fix.
Bootstrap from 0.0.0 (an unpublished marker) and commit 36a04fd so the first expected 0.1.0 release includes document deletion without inventing older release history. The changelog records deletion behavior and deployment caveats. No API runtime, assembly version, migration or Render configuration changes.
Add CI for .NET 10 restore/build/test/publish and release metadata checks. Pin actions to immutable commits. Tag publication checks version-matched notes and main ancestry, then clears the release PR's pending label.
Validation: seven release tooling tests pass; official configuration schema, workflow YAML/shell and action pins validate; Release build succeeds without warnings; 180 API tests pass (six external PostgreSQL/RabbitMQ integration tests skipped); dotnet publish succeeds.
The API repository must allow GitHub Actions to create pull requests, separately from the frontend setting.