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
Simplify & automate the release process #6482
Comments
mathiasbynens
added a commit
that referenced
this issue
Oct 8, 2020
This patch sets up commitlint to enforce the Conventional Commits format. This check runs with the other lint checks as part of npm run lint, and a Git commit hook is set up via Husky for automated local checks. Issue: #6482
mathiasbynens
added a commit
that referenced
this issue
Oct 8, 2020
This patch sets up commitlint to enforce the Conventional Commits format. This check runs with the other lint checks as part of npm run lint, and a Git commit hook is set up via Husky for automated local checks. Issue: #6482
mathiasbynens
added a commit
that referenced
this issue
Oct 22, 2020
mathiasbynens
added a commit
that referenced
this issue
Oct 23, 2020
mathiasbynens
added a commit
that referenced
this issue
Oct 29, 2020
As long as we follow Conventional Commits for our commit messages (which is now enforced since #6483), we can automate the maintenance of this new changelog, which enables us to later automate the release process altogether. This patch also eliminates the versioning decision-making process by automating it based on our commit messages. Issue: #6482
mathiasbynens
added a commit
that referenced
this issue
Oct 29, 2020
As long as we follow Conventional Commits for our commit messages (which is now enforced since #6483), we can automate the maintenance of this new changelog, which enables us to later automate the release process altogether. This patch also eliminates the versioning decision-making process by automating it based on our commit messages. Issue: #6482
mathiasbynens
added a commit
that referenced
this issue
Oct 29, 2020
mathiasbynens
added a commit
that referenced
this issue
Oct 29, 2020
mathiasbynens
added a commit
that referenced
this issue
Nov 2, 2020
The npm dist tags are not worth the hassle, and are arguably harmful to the Web. Developers should feel encouraged to always test the latest available Puppeteer & Chromium versions, as opposed to any specific version. Issue: #6482
mathiasbynens
added a commit
that referenced
this issue
Nov 3, 2020
The npm dist tags are not worth the hassle, and are arguably harmful to the Web. Developers should feel encouraged to always test the latest available Puppeteer & Chromium versions, as opposed to any specific version. Issue: #6482
mathiasbynens
added a commit
that referenced
this issue
Nov 4, 2020
The npm dist tags are not worth the hassle, and are arguably harmful to the Web. Developers should feel encouraged to always test the latest available Puppeteer & Chromium versions, as opposed to any specific version. Issue: #6482
mathiasbynens
added a commit
that referenced
this issue
Nov 25, 2020
mathiasbynens
added a commit
that referenced
this issue
Nov 26, 2020
mathiasbynens
added a commit
that referenced
this issue
Nov 26, 2020
This was referenced Jun 6, 2021
Closed
1 task
This was referenced Jun 10, 2021
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
npm publish
when pushing new Git tags (chore: automate publishing on new Git tags #6536; example run)Note: Although step 0.5 is not part of the longer-term plan, it’s a relatively small change that already reduces the amount of manual steps in the release process significantly in the mean time.
The text was updated successfully, but these errors were encountered: