chore: fix changelog workflow

[bluwy]

🔗 Linked issue

n/a

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Follow-up for #773

My bad, I didn't notice jiti was still used for executing scripts in CI. I notice that we can execute TS directly with node, so I updated to do so instead, but let me know if you'd prefer using jiti like before instead.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/fonts@776

commit: d6ac7d5

[coderabbitai]

📝 Walkthrough

Walkthrough

These changes coordinate a shift in how the changelog update script is executed. The GitHub Actions workflow is modified to invoke the script using node directly instead of pnpm jiti, and correspondingly, the TypeScript source file's import statement is updated to explicitly include the .ts file extension to ensure proper module resolution with the new runtime approach.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: fix changelog workflow' accurately reflects the main change—fixing the CI workflow by replacing pnpm jiti with node execution.
Description check	✅ Passed	The description is directly related to the changeset, explaining the context (follow-up to PR #773), the issue (jiti still used in CI), and the solution (using node instead).

_{✏️ 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

---

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

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 66.78%. Comparing base (c60e4e3) to head (d6ac7d5).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #776   +/-   ##
=======================================
  Coverage   66.78%   66.78%           
=======================================
  Files           9        9           
  Lines         286      286           
  Branches       64       64           
=======================================
  Hits          191      191           
  Misses         78       78           
  Partials       17       17           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[danielroe]

no, i definitely prefer native execution! ❤️