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

fix: bump semantic release to allow node version 18 #660

Merged
merged 1 commit into from
Feb 5, 2024
Merged

Conversation

Scra3
Copy link
Member

@Scra3 Scra3 commented Feb 5, 2024

Definition of Done

General

  • Write an explicit title for the Pull Request, following Conventional Commits specification
  • Test manually the implemented changes
  • Validate the code quality (indentation, syntax, style, simplicity, readability)

Security

  • Consider the security impact of the changes made

@Scra3 Scra3 merged commit 76d81e8 into main Feb 5, 2024
8 checks passed
@Scra3 Scra3 deleted the bum-again branch February 5, 2024 14:56
forest-bot added a commit that referenced this pull request Feb 5, 2024
# [5.0.0](v4.3.4...v5.0.0) (2024-02-05)

### Bug Fixes

* bump semantic release to allow node version 18 ([#660](#660)) ([76d81e8](76d81e8))
* bump semantic release to allow node version 18 ([#661](#661)) ([11fefcd](11fefcd))
* upgrade semantic-release ([#662](#662)) ([d019f35](d019f35))

### BREAKING CHANGES

* users will have to upgrade to Node.js version 18 or above to ensure a full compatibility
Co-authored-by: Nicolas Moreau <[email protected]>
* users will have to upgrade to Node.js version 18+ to ensure a full compatibility
* users will have to upgrade to Node.js version 18+ to ensure a full compatibility
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