Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(run): update docs for v6 #3366

Merged
merged 2 commits into from Oct 12, 2022
Merged

fix(run): update docs for v6 #3366

merged 2 commits into from Oct 12, 2022

Conversation

vsavkin
Copy link
Contributor

@vsavkin vsavkin commented Oct 12, 2022

Description

Motivation and Context

How Has This Been Tested?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (change that has absolutely no effect on users)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@JamesHenry JamesHenry changed the title Docs changes v6b fix(run): update docs for v6 Oct 12, 2022
@JamesHenry JamesHenry merged commit 62b1fc8 into next Oct 12, 2022
@JamesHenry JamesHenry deleted the docs-changes-v6b branch October 12, 2022 16:26
JamesHenry pushed a commit that referenced this pull request Oct 12, 2022
@boneskull
Copy link

Was there some announcement about what, if anything, v6 broke?

@JamesHenry
Copy link
Member

@boneskull anything not covered in the release notes (or given as direct feedback when running commands) would be an unexpected breakage and should please be reported as a fresh issue. The upgrade path should be very smooth for most!

rrhodes pushed a commit to rrhodes/lerna that referenced this pull request Jan 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants