Skip to content
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

chore: release v1.4.0 #68

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Oct 13, 2024

🤖 I have created a release beep boop

1.4.0 (2024-10-13)

Features

  • no-release: add conditional support in #if (#72) (2f8e7da)
  • update headers from nodejs/node tag v22.7.0 (#48) (6c73c34)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-api-headers branch from 7b45673 to 2deb892 Compare October 13, 2024 16:07
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-api-headers branch 2 times, most recently from 11137d5 to ffd7049 Compare October 13, 2024 16:12
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-api-headers branch 2 times, most recently from 04f6668 to 23f96bb Compare October 13, 2024 16:16
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-api-headers branch from 23f96bb to bdf57ef Compare October 13, 2024 16:16
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-api-headers branch from bdf57ef to df126aa Compare October 13, 2024 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants