Actualizacion maquina principal

[dotfiles/.git] / .config / coc / extensions / node_modules / coc-prettier / node_modules / stylelint / docs / developer-guide / releases.md

diff --git a/.config/coc/extensions/node_modules/coc-prettier/node_modules/stylelint/docs/developer-guide/releases.md b/.config/coc/extensions/node_modules/coc-prettier/node_modules/stylelint/docs/developer-guide/releases.md
new file mode 100644 (file)
index 0000000..7920252
--- /dev/null
+++ b/.config/coc/extensions/node_modules/coc-prettier/node_modules/stylelint/docs/developer-guide/releases.md
@@ -0,0 +1,56 @@
+# Performing releases
+
+The primary goals are:
+
+1.  Publishing the updated package to npm.
+2.  Creating a GitHub release with notes.
+
+The secondary goals are:
+
+1.  Ensuring the stylelint org's `stylelint-config-*` shareable configs are compatible with the release.
+2.  Updating the online demo at [https://stylelint.io/demo](https://stylelint.io/demo) to use the release.
+3.  Updating the documentation at [https://stylelint.io](https://stylelint.io) to use the release.
+4.  Sending out a tweet.
+
+## Process
+
+1.  Create a [new issue](https://github.com/stylelint/stylelint/issues/new) announcing the planned release, e.g. `Release 8.11.1` and include the [template checklist](#new-release-issue-template).
+2.  Locally test `master` in the `stylelint-config-*` shareable configs repos.
+3.  Locally test `master` in the `stylelint.io` repo.
+4.  Locally test `master` in the `stylelint-demo` repo.
+5.  Both the publishing of the package to npm and the creating a github release are done with [`npmpub`](https://github.com/MoOx/npmpub):
+    1.  Ensure the CHANGELOG is [consistently formatted](pull-requests.md).
+    2.  Run `npm --no-git-tag-version version major|minor|patch` to increment the `version` number in `package.json` and `package-lock.json`, according to whether it's a patch, minor or major release.
+    3.  Replace `# Head` in `CHANGELOG.md` with this new version number e.g. `# 8.1.2`
+    4.  Commit and _push up_ these changes.
+    5.  Go to [https://github.com/stylelint/stylelint](https://github.com/stylelint/stylelint) and confirm these changes are correct and pushed up.
+    6.  Run `npm run dry-release`.
+    7.  Run `npm run release`.
+    8.  Go to [https://www.npmjs.com/package/stylelint](https://www.npmjs.com/package/stylelint) and confirm the package was published correctly.
+    9.  Go to [https://github.com/stylelint/stylelint/releases](https://github.com/stylelint/stylelint/releases) and confirm the release was created correctly.
+6.  If a new version of any `stylelint-config-*` is required, repeat step 3 for that repo.
+7.  Update the online demo by changing to the `stylelint-demo` repo:
+    1.  Run `npm install -S stylelint@latest`
+    2.  Run `npm test`
+    3.  Commit and _push up_ these changes.
+    1.  Go to [https://stylelint.io/demo](https://stylelint.io/demo) and confirm the update was automatically deployed.
+8.  Update the website documentation by changing the to `stylelint.io` repo:
+    1.  Run `npm install -D stylelint@latest`
+    2.  Run `npm test`
+    3.  Commit and _push up_ these changes.
+    4.  Run `npm run deploy`.
+    5.  Go to [https://stylelint.io](https://stylelint.io) and confirm the update was deployed correctly.
+9.  Compose a tweet that announces the release, communicates what has changed and links to the appropriate heading in the CHANGELOG on [https://stylelint.io](https://stylelint.io).
+
+## New Release Issue Template
+
+```markdown
+- [ ] stylelint release
+- [ ] stylelint-config-recommended update/release
+- [ ] stylelint-config-standard update/release
+- [ ] stylelint-demo update
+- [ ] stylelint.io update
+- [ ] tweet
+
+cc @stylelint/core
+```