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: allow specifying a deprecation message regardless of stability #146

Merged
merged 1 commit into from
Jun 13, 2023

Conversation

RomainMuller
Copy link
Contributor

Previously, jsii required the package's stability to be deprecated if there cas a deprecated message configured. This is however problematic when a stable package reaches End-of-Support and the maintainer wants to signal this in npmjs.com.

Instead of failing, only log a warning to possibly raise awareness on an unintended configuration.

Foward-ports: aws/jsii#4145


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

Previously, `jsii` required the package's stability to be `deprecated` if there cas a `deprecated` message configured. This is however problematic when a `stable` package reaches End-of-Support and the maintainer wants to signal this in npmjs.com.

Instead of failing, only log a warning to possibly raise awareness on an unintended configuration.

Foward-ports: aws/jsii#4145
@aws-cdk-automation aws-cdk-automation added this pull request to the merge queue Jun 13, 2023
Merged via the queue into main with commit 545015c Jun 13, 2023
@aws-cdk-automation aws-cdk-automation deleted the rmuller/deprecated branch June 13, 2023 13:29
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