Repository navigation
docs(release-notes): start the changes since v0.1.0-rc10 - #14478
Merged
Merged
Conversation
Relabel the changes and breaking changes listed since v0.1.0-rc9 as v0.1.0-rc10's, add empty sections for changes since v0.1.0-rc10, and give the breaking changes before v0.1.0-rc9 their own heading. Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Collaborator
Author
Authoring session — opening
|
Contributor
|
v1 documentation preview: https://nvidia-preview-nemoclaw-v1-pr-14478.docs.buildwithfern.com/nemoclaw |
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 v1 release notes now list
v0.1.0-rc10's changes under their own headings and start "sincev0.1.0-rc10" sections, so contributors add new entries there and readers can tell what the release candidate contains.Problem
docs/about/release-notes.mdlists everything that reachedv1after thev0.1.0-rc9tag under "Changes Since v0.1.0-rc9".v0.1.0-rc10is being tagged on 5716c39 (#14429), so those entries are now rc10's contents, and later changes need a separate place. rc9 left no per-candidate section, so this sets the convention.Change
v1between thev0.1.0-rc9andv0.1.0-rc10tags.updatePolicy: Preserveand the removedspec.gateway.image) were already inv0.1.0-rc9, so they get an "Earlier Breaking Changes" heading instead of falling under rc10's.#changes-since-v010-rc9anchor,#breaking-changes-and-migrationstill exists, and no contributing guide names the section.v0.1.0-rc10tag move to the sections sincev0.1.0-rc10, so those sections no longer say "None yet." The rc10 sections matchv0.1.0-rc10:docs/about/release-notes.md, including its pinned component versions.