[New gcm-core version] GCM 2.0.877

[github-actions[bot]]

build(deps): bump lycheeverse/lychee-action from 1.5.2 to 1.5.4 (#955)

Bumps
[lycheeverse/lychee-action](https://github.com/lycheeverse/lychee-action)
from 1.5.2 to 1.5.4.

Release notes

Sourced from lycheeverse/lychee-action's]() releases.

Version 1.5.4

What's Changed

• Cleanup old lychee bin after install by @​mre@%E2%80%8Bmre in lycheeverse/lychee-action#172lycheeverse/lychee-action#172

Full Changelog: https://github.com/lycheeverse/lychee-action/compare/v1...v1.5.4https://github.com/lycheeverse/lychee-action/compare/v1...v1.5.4

Version 1.5.3

What's Changed

• Bump lychee version to fix issues with email checking by @​mre@%E2%80%8Bmre in lycheeverse/lychee-action#171lycheeverse/lychee-action#171

Full Changelog: https://github.com/lycheeverse/lychee-action/compare/v1...v1.5.3https://github.com/lycheeverse/lychee-action/compare/v1...v1.5.3

Commits

• 4dcb8be4dcb8be bump version
• 0682ed60682ed6 Cleanup old lychee bin after install (#172)#172)
• 02de23102de231 Update lychee-actionn release in docs
• 0fcec0b0fcec0b Bump lychee version (#171)#171)
• See full diff in compare](https://github.com/lycheeverse/lychee-action/compare/25f59e1bc8f12b314a1e366f825e00d13de2d80b...4dcb8bee2a0a4531cba1a1f392c54e8375d6dd81%22>compare) view

[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=lycheeverse/lychee-action&package-manager=github_actions&previous-version=1.5.2&new-version=1.5.4)\

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`.

[…

---

Would you like to know more?

Read the full article on the following website:

https://github.com/GitCredentialManager/git-credential-manager/releases/tag/v2.0.877

[dscho]

I had originally meant to use this opportunity to drive forward the initiative to move Git for Windows' Pacman package deployments to GitHub workflows (mentioned here, there and there).

However, I'll take a break from that because I have hit a hard bump with the question how to build Pacman packages with gated secrets (which currently requires the usage of an "environment", which unfortunately is implicitly assumed to be connected to a deployment, but we do not even want to deploy anything there).

So I went ahead and started a build using the trusty old Azure Pipeline, still.

[dscho]

So I went ahead and started a build using the trusty old Azure Pipeline, still.

And that one succeeded.