Software zum Installieren eines Smart-Mirror Frameworks , zum Nutzen von hochschulrelevanten Informationen, auf einem Raspberry-Pi.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

releases.md 2.6KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647
  1. # Performing releases
  2. 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).
  3. 2. Locally test `master` in the `stylelint-config-*` shareable config repositories. Install current `master` branch (`npm install stylelint/stylelint#master`) and run tests.
  4. 3. Locally test `master` in the [stylelint/stylelint.io](https://github.com/stylelint/stylelint.io) repository.
  5. 4. Locally test `master` in the [stylelint/stylelint-demo](https://github.com/stylelint/stylelint-demo) repository.
  6. 5. Publish the package to npm and create a GitHub release using [`np`](https://github.com/sindresorhus/np):
  7. 1. [Consistently format](pull-requests.md) the [changelog](../../CHANGELOG.md).
  8. 2. Replace `## Head` with new version number e.g. `## 8.1.2`.
  9. 3. Commit these changes.
  10. 4. Push these changes.
  11. 5. Confirm the changes are correct at [https://github.com/stylelint/stylelint](https://github.com/stylelint/stylelint).
  12. 6. Run `npm run release`.
  13. 7. Select the version that matches the one from the changelog.
  14. 8. Copy and paste the changelog entries for the published version from [changelog](../../CHANGELOG.md) when the GitHub release page opens.
  15. 9. Confirm the publishing of the package to [https://www.npmjs.com/package/stylelint](https://www.npmjs.com/package/stylelint).
  16. 10. Confirm the creation of the release at [https://github.com/stylelint/stylelint/releases](https://github.com/stylelint/stylelint/releases).
  17. 6. If a new version of any `stylelint-config-*` is required, repeat step 5 for that repository.
  18. 7. Update the online demo by changing to the `stylelint-demo` repository:
  19. 1. Run `npm install -S stylelint@latest`.
  20. 2. Run `npm test`.
  21. 3. Commit these changes.
  22. 4. Push these changes.
  23. 5. Confirm the deployment of the update to [stylelint.io/demo](https://stylelint.io/demo).
  24. 8. Update the website documentation by changing to the `stylelint.io` repository:
  25. 1. Run `npm install -D stylelint@latest`.
  26. 2. Run `npm test`.
  27. 3. Commit these changes.
  28. 4. Push these changes.
  29. 5. Confirm the deployment of the update to [stylelint.io](https://stylelint.io).
  30. 9. Compose a tweet that:
  31. - announces the release
  32. - communicates what has changed
  33. - links to the appropriate heading in the changelog on [stylelint.io](https://stylelint.io).
  34. ## New release issue template
  35. ```markdown
  36. - [ ] stylelint release
  37. - [ ] stylelint-config-recommended update/release
  38. - [ ] stylelint-config-standard update/release
  39. - [ ] stylelint-demo update
  40. - [ ] stylelint.io update
  41. - [ ] tweet
  42. cc @stylelint/core
  43. ```