infra(release): check release PR

[ST-DDT]

This implements the second step of our automated release pipeline.

Tasks:

• Checkout faker
• Checkout playground
• Install pnpm
• Setup node
• Install deps - faker
• Build - faker
• Install deps - playground
• Build - playground
• Test - playground

---

Demo PRs:

• Release PR
  • chore: demo PR for release PRs ST-DDT/faker#15
  • https://github.com/ST-DDT/faker/actions/runs/9742754375/job/26884700385?pr=15
• Non-Release PR
  • chore: demo PR for non-release PRs ST-DDT/faker#14
  • https://github.com/ST-DDT/faker/actions/runs/9742749787/job/26884685270?pr=14

---

Automated Release Pipeline PRs:

1. infra(release): prepare release PR #2981
2. infra(release): check release PR #2988
3. infra(release): draft release #2990
4. infra(release): publish release #2991

[netlify]

✅ Deploy Preview for fakerjs ready!

Name	Link
🔨 Latest commit	a1a5a68
🔍 Latest deploy log	https://app.netlify.com/sites/fakerjs/deploys/66848681fe51120008045b0f
😎 Deploy Preview	https://deploy-preview-2988.fakerjs.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.96%. Comparing base (f104dd5) to head (a1a5a68).

Additional details and impacted files

@@           Coverage Diff            @@
##             next    #2988    +/-   ##
========================================
  Coverage   99.96%   99.96%            
========================================
  Files        2747     2747            
  Lines      239079   239079            
  Branches      591      944   +353     
========================================
+ Hits       238999   239000     +1     
+ Misses         80       79     -1     

see 1 file with indirect coverage changes

[Shinigami92]

I would potentially have some questions, but I think I can approve it for now

e.g.:

• should we think about to always run this check? I mean for any PR 🤔
• why should it only run on modified changelog.md

[ST-DDT]

• should we think about to always run this check? I mean for any PR 🤔

We could do that but it has a side effect, that all features that are used in the playground that might experience breaking changes need to be updated to the new feature before it is available as a dependency. This is also the case for the releasenPR but that those are even rarer.
In the end it doesnt matter.

[ST-DDT]

• why should it only run on modified changelog.md

There is no filter for release branches and that file is the best indicator for a release branch afaict.