Bump bcprov-jdk18on from 1.71 to 1.74

[dependabot[bot]]

Bumps bcprov-jdk18on from 1.71 to 1.74.

Changelog

Sourced from bcprov-jdk18on's changelog.

2.1.1 Version Release: 1.76 Date:      TBD

2.2.1 Version Release: 1.75 Date:      2023, June 21st

2.3.1 Version Release: 1.74 Date:      2023, June 12th

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/jitsi/libjitsi/network/alerts).

[JonathanLennox]

The Windows Native build failed, so this didn't get deployed - any ideas?

[ibauersachs]

I don't see the logs right now, could be an issue with VCPKG unable to download some mingw packages. Or it simply needs a retry.

[damencho]

The windows is about downloading grep, that's easy to fix.

But the Linux builds that fail are strange

  cat <(echo -e "") | gpg --batch --import
  gpg --list-secret-keys --keyid-format LONG
  shell: /usr/bin/bash -e {0}
  env:
    RELEASE_JAVA_VERSION: 11
    UBUNTUTOOLS_UBUNTU_MIRROR: http://azure.archive.ubuntu.com/ubuntu
    UBUNTUTOOLS_DEBIAN_MIRROR: http://debian-archive.trafficmanager.net/debian/
    UBUNTUTOOLS_DEBSEC_MIRROR: http://debian-archive.trafficmanager.net/debian-security
    DEBIAN_FRONTEND: noninteractive
    GPG_PASSPHRASE: 
gpg: directory '/home/runner/.gnupg' created
gpg: keybox '/home/runner/.gnupg/pubring.kbx' created
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
Error: Process completed with exit code 2.

Any idea bout those?

[damencho]

Hum, actually I created a PR to update to latest vcpkg release and everything is green there. So that should fix it.

[ibauersachs]

The PR came from Jonathans fork, and forks don't have access to secrets.

I should probably rewrite the pipelines so that PR builds don't require any secrets to be 'green' but that's a different story.