* fix: use version name in release notes
* fix: omit previously-released notes
* fix: sniff semantic commit types from PR subjects
instead of only from commit messages
* fix: do not use unrecognized semantic commit types
* chore: do not hardcode Release-Notes comment text
It used to be '<!-- One-line Change Summary Here-->',
it's currently a link to a best-practices page, and
it'll probably change again in the future. Let's just
match on <!--.*--> instead.
* chore: copyedit the help page
* chore: use clerk's OMIT_FROM_RELEASE_NOTES_KEYS
* chore: tweak comments
* chore: rename 'breaks' property as 'breaking'
* fix: use PR 'Notes' comment in release notes
* fix: follow links in roller-bot PRs
* refactor: better reference point version selection
* if we're a stable release, use the current brnach's previous stable
* if we're a beta release, use the current branch's previous beta
* if no match found, use the newest stable that precedes this branch
* refactor: dedup the caching functions' code
* refactor: partially rewrite release note generator
* parse release notes comments from PRs
* do not display no-notes PRs
* handle roller-bot commits by following cross-repo commits/PRs
* minor tweaks to note rendering, e.g. capitalization
* fix: fix lint:js script typo
* fix: copy originalPr value to rollerbot PR chains
* fix: handle more cases in release notes generator
* handle force-pushes where no PR
* better type guessing on pre-semantic commits
* fix: handle more edge cases in the note generator
* better removal of commits that landed before the reference point
* ensure '<!-- One-line Change Summary Here-->' is removed from notes
* handle more legacy commit body notes e.g. "Chore(docs)"
* check for fix markdown in PR body e.g. a link to the issue page
* chore: tweak code comments
* refactor: easier note generator command-line args
* refactor: group related notes together
* feat: query commits locally for gyp and gn deps
* chore: slightly better filtering of old commits
* feat: omit submodule commits for .0.0 releases
More specifically, only include them if generating release
notes relative to another release on the same branch.
Before that first release, there's just too much churn.
* refactor: make release-notes usable as a module
Calling it from the command line and from require()() now
do pretty much the same thing.
* refactor: passing command-line args means use HEAD
* chore: plug in the release note generator
* feat: support multiline 'Notes:' messages.
xref: https://github.com/electron/trop/pull/56
xref: https://github.com/electron/clerk/pull/16
* remove accidental change in package.json
* simplify an overcomplicated require() call
* Don't use PascalCase on releaseNotesGenerator()
* Remove code duplication in release notes warnings
* remove commented-out code.
* don't use single-character variable names.
For example, use 'tag' instead of 't'. The latter was being
used for map/filter arrow function args.
* Look for 'backport' rather than 'ackport'.
* Wrap all block statements in curly braces.
* fix tyop
* fix oops
* Check semver validity before calling semver.sort()
* test: add an option to native tests runner to run also disabled tests
* ci: run all native tests on clean Chromium
* ci: update the disabled tests list for native unittests
* ci: run unittests on clean Chromium
* test: add '--run-only-disabled-tests' flag to "script/native-tests.py"
* ci: add a job to run only disabled unittests
* test: use a different GN config for the native tests
* test: enable blink_common_unittests
* test: disable WeakPtrDeathTest*
