fixed links to contributors and backers for opencollective.com server target.

* fix(git): replace removed `git whatchanged` with `git log --raw --no-merges`

Modern git refuses to run `git whatchanged` without `--i-still-use-this`,
causing every CI build to fail in the test step and blocking all PRs.
Switch to the equivalent `git log --raw --no-merges` that git itself
suggests as the replacement; raw output format is unchanged so existing
consumers continue to work.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* ci: modernize Node matrix to 18/20/22

Node 12, 14, and 16 are all past EOL (April 2022, April 2023, and
September 2023 respectively). Node 12 in particular started failing
because a transitive dep now ships optional chaining / nullish
coalescing, which isn't supported until Node 14.

Replace the matrix with the currently maintained LTS line (18/20/22)
and bump `engines.node` to `>= 18` to match.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* ci: install pnpm via npm and drop broken store-dir config

The previous Setup pnpm step used a 2021-era install script for pnpm@6
and then ran `pnpm config set store-dir $(pnpm_config_cache)`. The
`pnpm_config_cache` variable was never defined as an Azure pipeline
variable, so the substitution produced an empty value and the config
command errored on newer Node/npm versions — failing the step.

Replace with `npm install -g pnpm`, which installs current pnpm on all
OSes without any cache plumbing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* ci: pin pnpm@9 and restrict logo regeneration to Linux

Two follow-up fixes for the Node 18/20/22 matrix:

- Pin pnpm to v9 (was unpinned, resolving to v10+). pnpm 10 changes
  default behavior around peer deps and corepack that breaks the
  `pnpm add` invocations in init tests on Node 22 specifically. pnpm 9
  is stable across the whole matrix.

- Only run `bash logo/generate.sh` on Linux. The script invokes Python's
  `cairosvg`, which requires the native Cairo C library; that's reliably
  available on the Linux runners but not on Windows/macOS. The step is
  a PNG regeneration utility, not a test — no need to gate the build on
  it for non-Linux jobs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

The release workflow currently uses `actions/checkout@v2` and
`actions/setup-node@v2`. Both run on the long-deprecated Node 16
action runtime, and `setup-node@v2` talks to GitHub's v1 cache
service, which now returns HTTP 400 — failing the release job
before it can run `npx semantic-release`.

Bump both to v4 (current). No other changes needed.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Grant id-token write permission, upgrade npm to a version that supports
trusted publishing, and drop NPM_TOKEN so semantic-release authenticates
to the registry via OIDC instead of a long-lived token.

Co-authored-by: Pietro Bongiovanni <pietro.bongiovanni@mollie.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…1029)

@semantic-release/npm gained support for npm trusted publishing (OIDC)
in v12.0.2, which requires semantic-release >= 24. The previous pin of
semantic-release@19.0.5 / @semantic-release/npm@9.0.1 hard-failed in
verifyConditions with ENONPMTOKEN before npm ever got a chance to use
the OIDC flow configured on the registry.

This upgrade pulls in @semantic-release/npm@13 and
@semantic-release/github@12 transitively, so the release workflow can
finally authenticate via OIDC.

Co-authored-by: Pietro Bongiovanni <pietro.bongiovanni@mollie.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>