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

Remove @next specifiers in docs & READMEs #21952

Merged
merged 1 commit into from
Apr 5, 2023

Conversation

kylegach
Copy link
Contributor

@kylegach kylegach commented Apr 5, 2023

What I did

  • Change all relevant instances of @next to @latest, to ensure the best version is installed/used

How to test

Follow the documentation contribution instructions for this branch, more-next-to-latest-snippets.

Checklist

  • Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
  • Make sure to add/update documentation regarding your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Maintainers

  • If this PR should be tested against many or all sandboxes,
    make sure to add the ci:merged or ci:daily GH label to it.
  • Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

@kylegach kylegach added documentation patch:yes Bugfix & documentation PR that need to be picked to main branch labels Apr 5, 2023
@kylegach kylegach self-assigned this Apr 5, 2023
@kylegach kylegach changed the title Change @next to @latest in Migration guide Change @next to @latest in docs & READMEs Apr 5, 2023
- If attached to a library used via npx/pnpm dlx, change to `@latest`
- Otherwise, remove it
@kylegach kylegach force-pushed the more-next-to-latest-snippets branch from 1d1357c to 15623ce Compare April 5, 2023 16:45
@kylegach kylegach changed the title Change @next to @latest in docs & READMEs Remove @next specifiers in docs & READMEs Apr 5, 2023
Copy link
Contributor

@jonniebigodes jonniebigodes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, thanks for taking care of this and making the required changes @kylegach , merge when able

@kylegach kylegach merged commit ddddc93 into next Apr 5, 2023
16 checks passed
@kylegach kylegach deleted the more-next-to-latest-snippets branch April 5, 2023 17:57
@shilman shilman added the patch:done Patch/release PRs already cherry-picked to main/release branch label Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation patch:done Patch/release PRs already cherry-picked to main/release branch patch:yes Bugfix & documentation PR that need to be picked to main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants