[CMSDS-3756] Version 18.0 blog post#4081
Open
derek-cmsds wants to merge 8 commits into
Open
Conversation
Collaborator
tamara-corbalt
left a comment
There was a problem hiding this comment.
Looks great overall! Just a couple nits
|
|
||
| ## Unified version numbers | ||
|
|
||
| Starting with this release of the CMS Design System, we will renumber our releases to unify all packages to a single version number. This release was slated to be version 14 of Core & CMS, version 16 of Medicare and version 18 of Healthcare. We have decided to align to the highest version number, which in this case is version 18. |
Collaborator
There was a problem hiding this comment.
Minor suggestion: "We have decided to align to the highest version number" -> "We have decided to align with the highest version number"
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.
Summary
mainfirst and then cherry-picked into the release branch.How to test
npm startChecklist
[CMSDS-####] Titleor [NO-TICKET] if this is unticketed work.Type(only one) label for this PR, if it is a breaking change, label should only beType: BreakingImpacts, multiple can be selected.If this is a change to documentation/content: