Add Release Notes column to API reference versions table#225
Merged
petesramek merged 1 commit intodevelop/1.0from Apr 5, 2026
Merged
Add Release Notes column to API reference versions table#225petesramek merged 1 commit intodevelop/1.0from
petesramek merged 1 commit intodevelop/1.0from
Conversation
…orkflow Agent-Logs-Url: https://github.com/petesramek/polyline-algorithm-csharp/sessions/a802ecac-bc1a-45b3-8640-e763e21f4755 Co-authored-by: petesramek <2333452+petesramek@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
petesramek
April 5, 2026 18:30
View session
petesramek
approved these changes
Apr 5, 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
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.
The API reference landing page versions table had no link to per-version changelog/release notes.
Changes
publish-documentation.yml: Added a "Release Notes" column to the generated "Released Versions" table; each entry links to the corresponding GitHub Release page (releases/tag/v<version>), which is already auto-populated fromCHANGELOG.mdby the release workflow.The generated table now looks like: