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

feat(check-node): allow silencing @jsii/check-node warnings #3841

Merged
merged 7 commits into from
Nov 24, 2022

Conversation

RomainMuller
Copy link
Contributor

Allows silencing @jsii/check-node warnings when the runtime is not End-of-Life, so that users who know what they are doing can suppress the extraneous output.

This is particularly useful for new Node releases that are un-tested, but can typically be expected to work, or known broken releases that happen to work for a given use-case that is carefully crafted to avoid the known issues; but is also possible for deprecated node releases.

Messages about using end-of-life releases are intentionally not suppressible.

Also updated the message for un-tested and known-broken releases to better frame the fact that these might work fine, and urge users to retry using a known supported release before they file a bug report.

Additionally adds testing for Node 19.x.

Fixes #3817
Fixes #3171


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Allows silencing @jsii/check-node warnings when the runtime is not
End-of-Life, so that users who know what they are doing can suppress
the extraneous output.

This is particularly useful for new Node releases that are un-tested,
but can typically be expected to work, or known broken releases that
happen to work for a given use-case that is carefully crafted to avoid
the known issues; but is also possible for deprecated node releases.

Messages about using end-of-life releases are intentionally not
suppressible.

Also updated the message for un-tested and known-broken releases to
better frame the fact that these might work fine, and urge users to
retry using a known supported release before they file a bug report.

Fixes #3817
Fixes #3171
@RomainMuller RomainMuller requested a review from a team November 15, 2022 12:06
@RomainMuller RomainMuller self-assigned this Nov 15, 2022
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Nov 15, 2022
@RomainMuller RomainMuller changed the title feat: allow silencing @jsii/check-node warnings feat(check-node): allow silencing @jsii/check-node warnings Nov 15, 2022
@mergify
Copy link
Contributor

mergify bot commented Nov 23, 2022

Thank you for contributing! ❤️ I will now look into making sure the PR is up-to-date, then proceed to try and merge it!

@mergify mergify bot added the pr/ready-to-merge This PR is ready to be merged. label Nov 23, 2022
@mergify
Copy link
Contributor

mergify bot commented Nov 23, 2022

Merging (with squash)...

@mergify
Copy link
Contributor

mergify bot commented Nov 24, 2022

Merging (with squash)...

@RomainMuller RomainMuller merged commit 880dbcc into main Nov 24, 2022
@RomainMuller RomainMuller deleted the rmuller/test-node-19 branch November 24, 2022 13:14
@mergify mergify bot removed the pr/ready-to-merge This PR is ready to be merged. label Nov 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS.
Projects
None yet
2 participants