-
Notifications
You must be signed in to change notification settings - Fork 45
Version 0.16.0 beta.1 #162
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| { | ||
| "name": "@rescript/react", | ||
| "version": "0.16.0", | ||
| "version": "0.16.0-beta.1", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
When releasing this version with the matching Useful? React with 👍 / 👎. |
||
| "description": "React bindings for ReScript", | ||
| "files": [ | ||
| "README.md", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a tag such as
v0.16.0-beta.1passes this newly widened check, the publish step runsnpm publishwithout--tag; the npm publish documentation specifies that the tag defaults tolatestand is added to the submitted package. Publishing this beta would therefore replace@rescript/react'slatestversion, causing ordinary unversioned installs to receive a prerelease that requires an alpha ReScript runtime; select an explicit non-latestdist-tag wheneverPACKAGE_VERSIONis a prerelease.Useful? React with 👍 / 👎.