Updated left out warning statement

[daminichopra]

Proposed changes

Fixed some left out "warning" statement as "warn" is deprecated now

Types of changes

What types of changes does your code introduce to the project: Put an x in the boxes that apply

• [ x ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [ x ] I have read the CONTRIBUTING doc
• [ x ] I have signed the CLA
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ x ] I have updated the [RELEASE_NOTES][RELEASE_NOTES.md]
• [ ] I have added necessary documentation (if appropriate)
• [ ] Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

"Martel Open Source Software Individual Contributor License Agreement"

"Contributing to QuantumLeap"

[github-actions[bot]]

CLA Assistant Lite bot All contributors have signed the CLA ✍️

[daminichopra]

@chicco785 , Gentle Reminder for PR merge

[chicco785]

@chicco785 , Gentle Reminder for PR merge

hi, we move to 0.9.0-dev, i need you to rebase and append correctly your content to the release note, many thanks.

[c0c0n3]

@daminichopra I'd imagine we can close #606 after merging this PR?

[daminichopra]

@daminichopra I'd imagine we can close #606 after merging this PR?

@c0c0n3 yes Issue #606 can be closed after merging this PR.