fix: migrate to @wfcd/patchlogs

[TobiTenno]

What did you fix?

migrate to new @wcd/patchlogs library from warframe-patchlogs

---

Reproduction steps

new package name

---

Evidence/screenshot/link to line

Considerations

• Does this contain a new dependency? [Yes] technically, migrating from one to another
• Does this introduce opinionated data formatting or manual data entry? [No]
• Does this pr include updated data files in a separate commit that can be reverted for a clean code-only pr? [Yes]
• Have I run the linter? [Yes]
• Is is a bug fix, feature request, or enhancement? [Maintenance]

Summary by CodeRabbit

• Chores
  • Updated package dependency to a new version across build workflows and build scripts.
  • Updated test utilities to use an updated color handling approach.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR migrates the patchlogs dependency from warframe-patchlogs to @wfcd/patchlogs across GitHub Actions workflows, build scripts, and package.json. Additionally, pixel test utilities are replaced with colors utility implementation for color validation.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflows .github/workflows/build.yaml, regression.yaml, release.yaml, static.yaml	Replace warframe-patchlogs@^2 with @wfcd/patchlogs@^2 in npm install steps across all workflow files.
Build Scripts build/build.mjs, build/scraper.mjs	Update import statements and JSDoc type annotations from warframe-patchlogs to @wfcd/patchlogs module references.
Package Dependencies package.json	Replace devDependency warframe-patchlogs@^2.148.0 with @wfcd/patchlogs@^2.149.4.
Test Utilities test/utilities/pixel.spec.mjs	Replace Pixel utility import and instance creation with colors utility; update test assertions to use colors.safeColor(hex) function.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

• SlayerOrnstein
• AyAyEm

Poem

🐰 A hop, skip, and jump through the package tree,
From warframe-patchlogs to @wfcd we decree!
With colors so bright in our test suite now gleaming,
The workflows all dance with this refactoring beaming. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix: migrate to @wfcd/patchlogs' accurately summarizes the main change: migrating from warframe-patchlogs to @wfcd/patchlogs package across all workflow files, configuration, and code files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch wfcd-patchlogs

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

test/utilities/pixel.spec.mjs (1)

4-5: Stale describe labels: 'Pixel' and '#constructor' no longer reflect the code under test.

Now that the tests use colors.safeColor(), consider updating the describe blocks to match (e.g., 'colors' / '#safeColor').

Proposed fix

-describe('Pixel', () => {
-  describe('#constructor', () => {
+describe('colors', () => {
+  describe('#safeColor', () => {

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[wfcd-bot-boi]

🎉 This PR is included in version 1.1272.115 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀