docs: move release guide to RELEASING.md - #174
Merged
Merged
Conversation
marandaneto
enabled auto-merge (squash)
April 16, 2026 11:10
Contributor
Prompt To Fix All With AIThis is a comment left during a code review.
Path: README.md
Line: 74
Comment:
**Missing section header for release pointer**
The original content sat under a `## Publishing Releases` heading. Without it, this line reads as a stray paragraph inside the "Testing" section rather than its own navigable entry, which breaks the README's heading hierarchy and removes the TOC anchor.
```suggestion
## Publishing Releases
For release instructions, see [RELEASING.md](RELEASING.md).
```
How can I resolve this? If you propose a fix, please make it concise.Reviews (1): Last reviewed commit: "docs: move release guide to RELEASING.md" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| 3. Approve the release in the GitHub Environment gate (the workflow pauses for maintainer approval) | ||
| 4. The workflow bumps the version in `Directory.Build.props`, commits to `main`, creates a git tag, and creates a GitHub Release | ||
| 5. The GitHub Release triggers the [`main.yaml`](.github/workflows/main.yaml) workflow, which builds and publishes the packages to NuGet | ||
| For release instructions, see [RELEASING.md](RELEASING.md). |
Contributor
There was a problem hiding this comment.
The original content sat under a ## Publishing Releases heading. Without it, this line reads as a stray paragraph inside the "Testing" section rather than its own navigable entry, which breaks the README's heading hierarchy and removes the TOC anchor.
Suggested change
| For release instructions, see [RELEASING.md](RELEASING.md). | |
| ## Publishing Releases | |
| For release instructions, see [RELEASING.md](RELEASING.md). |
Prompt To Fix With AI
This is a comment left during a code review.
Path: README.md
Line: 74
Comment:
**Missing section header for release pointer**
The original content sat under a `## Publishing Releases` heading. Without it, this line reads as a stray paragraph inside the "Testing" section rather than its own navigable entry, which breaks the README's heading hierarchy and removes the TOC anchor.
```suggestion
## Publishing Releases
For release instructions, see [RELEASING.md](RELEASING.md).
```
How can I resolve this? If you propose a fix, please make it concise.
Contributor
posthog-dotnet Compliance ReportDate: 2026-04-16 11:11:37 UTC
|
| Test | Status | Duration |
|---|---|---|
| Request Payload.Request With Person Properties Device Id | ❌ | 44ms |
Failures
request_payload.request_with_person_properties_device_id
404, message='Not Found', url='http://sdk-adapter:8080/get_feature_flag'
dustinbyrne
approved these changes
Apr 16, 2026
This was referenced May 2, 2026
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
2 participants
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.
Problem
The release instructions only live in
README.md, which makes them harder to keep as a single source of truth across SDK repos.Changes
RELEASING.mdRELEASING.mdChecklist