Skip to content

chore: add release automation #43

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

Merged
merged 1 commit into from
Jul 9, 2024
Merged

chore: add release automation #43

merged 1 commit into from
Jul 9, 2024

Conversation

KevinEady
Copy link
Contributor

Refs: #13

@KevinEady
Copy link
Contributor Author

Hey @legendecas , I basically took your introduction of release-please to node-addon-api and made a few changes:

  • updated the version in the manifest to latest released version (1.1.0)
  • updated the commit sha in the manifest to sha of latest release tag (v1.1.0)
  • removed the README.md from the config extra files, as we do not state the package version there (only Node-API version, not sure if this can be automated)

PTAL

Copy link
Member

@legendecas legendecas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, Thanks!

Additionally, I think we need to update the generated commit message at:
https://github.com/nodejs/node-api-headers/blob/main/scripts/update-headers.js#L163 to follow the pattern like "feat: update ..." so that release-please can pick up the change and bump the version correctly.

@legendecas
Copy link
Member

Ah, it's being updated at #44.

@legendecas legendecas merged commit 033f7d3 into main Jul 9, 2024
@KevinEady KevinEady deleted the add-release-automation branch July 9, 2024 18:31
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.

2 participants