--allow-unreleased flag enabled still logs new Releases to StdErr, breaks CI

[BrennanAyers]

With the recent change to log to stderr (probably good!), our pipelines have started failing on any new Helm releases (this happens often to feature namespaces), even when using the --allow-unreleased flag. This was previously not an issue because the "error" was logged to stdout and therefor Azure Devops didn't care.
Maybe I am misunderstanding how that flag is supposed to be used, but I would understand it to not log an Error in the case it is set to True.

Example command:
helm diff upgrade --install --values $(Chart.Values) $(Chart.Release) "$(Chart.Path)" (which I think I also understand to not care about unreleased Charts, even without the specific flag)

Currently I have set our task to just Ignore Standard Error output, but that will lead to further problems down the road.
Some clarity on how/why this error message isn't being suppressed with the above command and/or allow-unreleased would be helpful.

Thanks!

[yxxhero]

@BrennanAyers what will happen when has stderr output?

[yxxhero]

@BrennanAyers do you have any good idea?

[BrennanAyers]

@yxxhero Sorry, my organization blocked uploading of images to Github for no reason. I've been working with them to get this restriction removed so I can show examples. Logs don't really show the problem since it would be the same text output but you wouldn't see the failure.

[dkadetov]

Based on this: #786 I would suggest trying 2>&1

[BrennanAyers]

@yxxhero Here's an example of when the library was logging to stdout:

Here's how it is now when it logs to stderr:

As I explained, we're currently just ignoring all errors logged on this step, but that feels bad and will lead to issues down the road if we have real problems that don't log. If that's how it's going to work, then so be it, but I'm mostly looking for clarity on why --allow-unreleased considers a new release to be an error state or how to stop the library from logging an error for a new release.
Thanks.

[yxxhero]

@dkadetov maybe when you enable --allow-unreleased flag. we shouldn't print the message.

[yxxhero]

@BrennanAyers

[dkadetov]

@yxxhero
Yes, I use --allow-unreleased flag. Just to prevent output to stderr I added 2>&1 to the end of the command. Thus the behavior remains the same as before the #786 For example, this is applicable for Azure DevOPs CI with failOnStandardError: true

[BrennanAyers]

Thank you for getting this merged in, I'm sure I won't be the only one who appreciates it!