Add Changelog TOC entry for osl-python-api 2026.R1.SP00 - #504
Open
lesliedove wants to merge 2 commits into
Open
Conversation
changelog.md existed but was not linked in toc.yml, so the portal sidebar never showed Changelog for base 26R1 (SP03 already had the TOC entry).
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.
Summary
toc.ymlforosl-python-api2026.R1.SP00so the developer portal sidebar shows the existingchangelog.md.Context
Melanie flagged that Changelog was visible in PR diffs but not on the portal for 26R1 — root cause was
changelog.mdpresent without a matchingtoc.ymlhref.Test plan
optislang-python-api-2026-r1-sp00shows Changelog in left nav/docs/optislang-python-api-2026-r1-sp00/changelog.md