-
Notifications
You must be signed in to change notification settings - Fork 10
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
release md v1 #370
release md v1 #370
Conversation
b315f29
to
4d26f09
Compare
For some reason, the package-lock bumped. Can you confirm why it happened? |
Prettier changed formatting a bit. |
You need to be a member of @livechat organization on npm. Then after authorization (`npm login`) you can publish packages into npm registry. | ||
|
||
To bump package versions and publish them into registry please run `npm run deploy`. | ||
We have entire document about that take a look [here](./RELEASE.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.
We have entire document about that take a look [here](./RELEASE.md). | |
Release process is described [here](./RELEASE.md). By default `@livechat` organization members are maintainers and have required permissions. |
I'm afraid that any new update in package.json will bring back the old formatting. O think we should exclude automatically generated files from linting rules. At this moment please skip the update of this file, and we'll reconfigure the linter in a separate PR. |
This reverts commit 888f27c.
first version of release howto