Skip to content

chore(ci): use Actions to generate changelog - #488

Merged
mmarchini merged 2 commits into
nodejs:masterfrom
mmarchini:release-please
Aug 21, 2020
Merged

mmarchini merged 2 commits into
nodejs:masterfrom
mmarchini:release-please

Conversation

@mmarchini

Copy link
Copy Markdown
Contributor

release-please will bump the package version and generate changelogs
based on conventionalcommit. It does so by opening a PR every time a
commit lands, and it updates that PR for each subsequent commit.
Publishing to npm is still done manually.

Ref: #446

@codecov

codecov Bot commented Aug 20, 2020 •

Copy link
Copy Markdown

Codecov Report

Merging #488 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #488   +/-   ##
=======================================
  Coverage   83.13%   83.13%           
=======================================
  Files          34       34           
  Lines        1696     1696           
=======================================
  Hits         1410     1410           
  Misses        286      286           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 855f1d4...eba88a4. Read the comment docs.

@mmarchini

Copy link
Copy Markdown
Contributor Author

cc @nodejs/node-core-utils this should offload some of the release process to Actions (we still need to publish it manually though).

Comment thread .github/workflows/commitlint.yml Outdated
`release-please` will bump the package version and generate changelogs
based on conventionalcommit. It does so by opening a PR every time a
commit lands, and it updates that PR for each subsequent commit.
Publishing to npm is still done manually.

Ref: nodejs#446
@mmarchini
mmarchini merged commit f66c27d into nodejs:master Aug 21, 2020
@mmarchini
mmarchini deleted the release-please branch August 21, 2020 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants