Repository navigation
Match the 2.6.0 changelog to the release notes - #370
Merged
Merged
Conversation
Adds how to switch to the OKLCH build and links to its docs, and lists PR 368 under Repository Changes and Documentation Changes too, as earlier releases do for PRs that touch several areas. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gavinomelia
approved these changes
Oct 22, 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
3 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.
Task
[OP-XXX](link to ticket)No ticket. Follow-up to #368.Why?
The 2.6.0 changelog entry should match the v2.6.0 release notes, which now say how to switch to the OKLCH build and list #368 under each area it changed, as earlier releases do.
What Changed
Quality Assurance
Add an X to all that apply like this: [X]
Cross out all that don't apply with ~~ ~~ around it like
this[ ] Have you tried building the css?[ ] Have you tried building storybook?[ ] Have you updated any usage of changed tokens?[ ] Did you add a component?[ ] Have you added it to the dependency graph?[ ] Have you added it to the docs?[ ] Did you update a component?[ ] Have you updated the dependency graph?[ ] Have you updated the docs?[ ] Do you need to update the package version?[ ] Did you update the example pages in.storybook/assets?[ ] Were any changes made to the top level optics.css file?[ ] Were those changes reflected in the other top level files?Screenshots
None. No UI changes.