Add docs to consume preview packages #544
Merged
Conversation
This file contains 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
timotheeguerin
requested review from
bterlson,
daviwil,
nguerrera,
markcowl and
allenjzhang
as code owners
|
You can try these changes at https://cadlplayground.z22.web.core.windows.net/prs/544/ |
markcowl
requested changes
May 18, 2022
README.md
Outdated
| On every commit to the main branch, packages with changes are automatically packaged and published under the `@next` tag under npm. | ||
| In the [packages](#packages) section each package has a `@next` tag which show its current next version. | ||
|
|
||
| To use a `nightly` version of the packages update go over each one of the packages in the `package.json` fie and update it to either the latest published `@next` version or `@latest`, which ever is the newest. (You can also use the tag `latest` or `next`) |
There was a problem hiding this comment.
Are we saying that they can use the tag 'next' or 'latest' in their package.json files? Or do we want them to be explicit about version and not use the tags?
There was a problem hiding this comment.
They can use either. For next I think it doesn't matter, next be maybe simpler. For latest we maybe should decide when we go to 1.0 if we want people to try to always use the latest version or be tied to a major, minor version
Co-authored-by: Mark Cowlishaw <[email protected]>
Co-authored-by: Mark Cowlishaw <[email protected]>
bterlson
approved these changes
May 23, 2022
Co-authored-by: Brian Terlson <[email protected]>
Co-authored-by: Brian Terlson <[email protected]>
Co-authored-by: Brian Terlson <[email protected]>
Co-authored-by: Brian Terlson <[email protected]>
markcowl
approved these changes
May 24, 2022
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.
fix #494