[nanojsonc] update 1.2.0

[saadshams]

• [x ] Changes comply with the maintainer guide.
• [x ] SHA512s are updated for each updated download.
• [x ] The "supports" clause reflects platforms that may be fixed by this new version.
• [x ] Any fixed CI baseline entries are removed from that file.
• [x ] Any patches that are no longer applied are deleted from the port's directory.
• [x ] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• [x ] Only one version is added to each modified port's versions file.

[saadshams]

Unable to upgrade the port to 1.2.0, please support.

[saadshams]

@LilyWangLL Please guide on what's missing?

[LilyWangLL]

Installing 3/3 nanojsonc:x64-windows@1.2.0...
Building nanojsonc:x64-windows@1.2.0...
-- Note: nanojsonc only supports static library linkage. Building static library.
Asset cache miss; downloading from https://github.com/open-source-patterns/nanojsonc/archive/1.2.0.tar.gz
Downloading open-source-patterns-nanojsonc-1.2.0.tar.gz
Failed to download open-source-patterns-nanojsonc-1.2.0.tar.gz.
If you are using a proxy, please ensure your proxy settings are correct.
Possible causes are:

1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable to https//address:port.
   This is not correct, because https:/// prefix claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr, etc...) is an HTTP proxy.
   Try setting http://address:port/ to both HTTP_PROXY and HTTPS_PROXY instead.
2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings set by your proxy software. See, If HTTP(S)_PROXY already exist in environment variable, do not use IE Proxy (#49) vcpkg-tool#77
   The value set by your proxy might be wrong, or have same https:/// prefix issue.
3. Your proxy's remote server is our of service.
   If you've tried directly download the link, and believe this is not a temporay download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
   to report this upstream download server failure.
   error: https://vcpkgassetcachewus.blob.core.windows.net/cache/8fe36b742b994598d6f5ae30433245f63da5378ff6866f593cf53916e2b2fdc5d85ddc88d20908fd1166c3568f62e2a8dd837270855cb603dad88246a726be51?*** SECRET ***: failed: status code 404
   error: File does not have the expected hash:
   url: https://github.com/open-source-patterns/nanojsonc/archive/1.2.0.tar.gz
   File: D:\downloads\open-source-patterns-nanojsonc-1.2.0.tar.gz.8340.part
   Expected hash: 8fe36b742b994598d6f5ae30433245f63da5378ff6866f593cf53916e2b2fdc5d85ddc88d20908fd1166c3568f62e2a8dd837270855cb603dad88246a726be51
   Actual hash: a83f38c67222d227faf352495b174a16ff6d5a0a45e9d6eda499ca6e8978d2dba184f820c7b726d80468a11fee02460cbd8b189d69a46716bd01c46e7b0607fd

[LilyWangLL]

You could get the failure log from https://dev.azure.com/vcpkg/public/_build/results?buildId=111732&view=logs&jobId=7922e5c4-0103-5f8f-ad17-45ce9bb98e80&j=7922e5c4-0103-5f8f-ad17-45ce9bb98e80&t=8ceef4ed-9be5-594f-e707-4e1dd58a3d21.

[LilyWangLL]

Please use command .\vcpkg x-add-version nanojsonc --overwrite-version to update the version file after you commit the new changes.

[saadshams]

@LilyWangLL I have updated SHA512 and added version programmatically after committing changes.

.\vcpkg x-add-version nanojsonc --overwrite-version

[LilyWangLL]

Please try not to manually modify the versions files (versions/baseline.json and versions/n-/nanojsonc.json ). After you finish updating the port-related codes, run command .\vcpkg x-add-version nanojsonc --overwrite-version, which will automatically update the version files. For reference, see the maintainer guide: https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md#versioning.

[saadshams]

remove supports field: OK
Leaving versions/baseline.json and versions/n-/nanojsonc.js intact.
Executed command .\vcpkg x-add-version nanojsonc --overwrite-version
Pushed the code.

[dg0yt]

Not resolved: Remove the "supports" line.

[saadshams]

Sorry. pushed the update without supports field.

[saadshams]

Thanks. all looks good, the approve field is disabled on my side
Is there an action item for me?

[saadshams]

Thanks. for information, how and from where the hash for git-tree is calculated?

[LilyWangLL]

Thanks. for information, how and from where the hash for git-tree is calculated?

You can refer to the documentation https://github.com/MicrosoftDocs/vcpkg-docs/blob/main/vcpkg/users/examples/versioning.getting-started.md#builtin-baseline.

[saadshams]

Hi @LilyWangLL I mean the following git-tree values, how and from where are they generated from

{
  "versions": [
    {
      "git-tree": "41dc847f236000b8a703cf452d37ae36c39ec155",
      "version": "1.2.0",
      "port-version": 0
    },
    {
      "git-tree": "102c65ad71dc556dd82d4af6d83efd96ee316311",
      "version": "1.1.0",
      "port-version": 0
    },
    {
      "git-tree": "7680709fd527db1cc26d47f8897c0669cacbfb0f",
      "version": "1.0.0",
      "port-version": 0
    }
  ]
}

[dg0yt]

This is how it works:
https://learn.microsoft.com/en-us/vcpkg/maintainers/registries#obtain-git-tree-sha