latest 2.1.11 has a new behaviour or a bug..??

[Concetta1941]

THE TRACKER IS DEDICATED TO KEEPING TRACK OF BUGS,
preferably after they have been already discussed and confirmed to be reproducible.

FOR ASSISTANCE, PLEASE CLOSE THIS FORM AND USE THE DISCUSSIONS SECTION INSTEAD:
https://github.com/DNSCrypt/dnscrypt-proxy/discussions/categories/q-a

Reported bugs must reproducible in the context described in the "Context" section.

Installation and configuration issues are not bugs, but individual assistance request.

Context: the LATEST version of `dnscrypt-proxy` (precompiled binaries downloaded from this repository) is correctly installed and configured on your system, but something doesn't seem to produce the expected result.

If the bug is not trivial to reproduce on any platform, please include ALL the steps required to reliably duplicate it, on a vanilla, generic install of macOS, Windows, OpenBSD or Ubuntu Linux system, in their most current version.

If you don't have any clear understanding of the issue or can't enumerate the steps to reproduce it, open a discussion instead:
https://github.com/DNSCrypt/dnscrypt-proxy/discussions


## Output of the following commands:

./dnscrypt-proxy -version

./dnscrypt-proxy -check

./dnscrypt-proxy -resolve example.com


- [ ] Initially raised as discussion #...



## *What* is affected by this bug?



## *When* does this occur?



## *Where* does it happen?


with the previous 2.1.8 if i start the dos powershell command:
N:\DESKTOP\PC\Dns\dnscrypt-proxy>   .\dnscrypt-proxy.exe -config dnscrypt-proxy.toml -check > dnscrypt-proxy.log
[2025-04-01 15:45:22] [NOTICE] dnscrypt-proxy 2.1.8
[2025-04-01 15:45:22] [NOTICE] Source [public-resolvers] loaded
[2025-04-01 15:45:22] [NOTICE] Source [relays] loaded
[2025-04-01 15:45:22] [NOTICE] Configuration successfully checked
PS N:\DESKTOP\PC\Dns\dnscrypt-proxy>



the first reply was the version number : 2.1.8

if i do the same with latest 2.1.11 i do not have that anymore:

PS N:\DESKTOP\PC\Dns\dnscrypt-proxy> .\dnscrypt-proxy.exe -config dnscrypt-proxy.toml -check > dnscrypt-proxy.log
[2025-05-23 12:17:16] [NOTICE] Source [public-resolvers] loaded
[2025-05-23 12:17:16] [NOTICE] Source [relays] loaded
[2025-05-23 12:17:16] [NOTICE] Configuration successfully checked
PS N:\DESKTOP\PC\Dns\dnscrypt-proxy>

of course i already control the log and it shows the correct number:
[2025-05-23 12:18:32] [NOTICE] dnscrypt-proxy 2.1.11
[2025-05-23 12:18:32] [NOTICE] Network connectivity detected
[2025-05-23 12:18:32] [NOTICE] Now listening to 127.0.0.1:53 [UDP]
[2025-05-23 12:18:32] [NOTICE] Now listening to 127.0.0.1:53 [TCP]
[2025-05-23 12:18:32] [NOTICE] Source [public-resolvers] loaded
[2025-05-23 12:18:32] [NOTICE] Source [relays] loaded
[2025-05-23 12:18:32] [NOTICE] Firefox workaround initialized
[2025-05-23 12:18:32] [NOTICE] Hot reload is disabled


so this is a new behaviour or a bug?
thxs in adv for yr kind cooperation
cheers
:)




## *How* do we replicate the issue?
<!-- Please list all the steps required to reliably replicate it, starting from a newly installed operating system -->



## Expected behavior (i.e. solution)



## Other Comments

[jedisct1]

Hi, thanks for the detailed report!

What you're observing is a change in behavior between versions, not a bug.

Starting with version 2.1.9, dnscrypt-proxy -check was slightly streamlined to only output the results strictly relevant to the configuration validation process. As a result, the initial version banner (e.g. dnscrypt-proxy 2.1.11) is no longer printed to the standard output when using -check. However, it's still available in the regular logs, as you correctly pointed out.

This was an intentional change to keep the output of -check focused and minimal—especially useful for automated systems that only care about whether the configuration is valid.

If you need to confirm the version explicitly, the recommended way is to run:

dnscrypt-proxy -version

Let me know if you think restoring the version banner in -check would be helpful for certain workflows.

[Concetta1941]

hi first so many thxs for yr kind reply
i can confirm that in powershell admin right we get the version:
Windows PowerShell
Copyright (C) Microsoft Corporation. Tutti i diritti riservati.

Prova la nuova PowerShell multipiattaforma https://aka.ms/pscore6

PS C:\WINDOWS\system32> cd N:
PS N:> cd N:\DESKTOP\PC\Dns
PS N:\DESKTOP\PC\Dns> cd N:\DESKTOP\PC\Dns\dnscrypt-proxy
PS N:\DESKTOP\PC\Dns\dnscrypt-proxy> .\dnscrypt-proxy -version
2.1.11
PS N:\DESKTOP\PC\Dns\dnscrypt-proxy>

you gently ask me if restoring the version banner in -check would be helpful
for me yes i prefer the old version when in -check we get for first information
the actual version installed, in this case 2.1.11
this is only my opinion
i thxs you again for having asked me this opinion
and for the kind attn and patience you have had with me.
cheers 👍