Skip to content

Conversation

@ovflowd
Copy link
Member

@ovflowd ovflowd commented May 2, 2025

This PR removes a console.log; removes vercel.json and switches to local fonts, because, yes.

Copilot AI review requested due to automatic review settings May 2, 2025 23:49
@ovflowd ovflowd requested a review from a team as a code owner May 2, 2025 23:49
@vercel
Copy link

vercel bot commented May 2, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview May 3, 2025 0:50am

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR removes a no longer needed console.log statement from the release data generator and switches font loading from external Google fonts to local assets.

  • Removed debug logging in releaseData.mjs
  • Updated font configurations in next.fonts.ts to use local fonts instead of remote fonts

Reviewed Changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.

File Description
apps/site/next.fonts.ts Updated to load fonts from local assets instead of Google fonts
apps/site/next-data/generators/releaseData.mjs Removed console.log debugging output
Files not reviewed (1)
  • apps/site/vercel.json: Language not supported

@codecov-commenter
Copy link

codecov-commenter commented May 2, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.83%. Comparing base (2f9f1b2) to head (35dddbf).

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7718   +/-   ##
=======================================
  Coverage   74.82%   74.83%           
=======================================
  Files          98       98           
  Lines        7878     7876    -2     
  Branches      199      199           
=======================================
- Hits         5895     5894    -1     
+ Misses       1982     1981    -1     
  Partials        1        1           

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

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ovflowd
Copy link
Member Author

ovflowd commented May 2, 2025

Vercel build will work once this gets merged (gotta remove the file overrides)

@ovflowd ovflowd added the github_actions:pull-request Trigger Pull Request Checks label May 2, 2025
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label May 2, 2025
Copy link
Member

@avivkeller avivkeller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per #7718 (comment)

We should not land this unless we can confirm, and prove, that the fonts we are using are from trusted sources.

@avivkeller avivkeller changed the title chore: local fonts and removed some weird files chore(next): remove vercel.json and extra log, update fonts May 3, 2025
@ovflowd
Copy link
Member Author

ovflowd commented May 3, 2025

Per #7718 (comment)

We should not land this unless we can confirm, and prove, that the fonts we are using are from trusted sources.

Why them being on a GitHub repository doesn't mean it came from an official source? All these fonts have very permissive licenses, so you can pretty much obtain them from anywhere. https://fonts.google.com/specimen/Open+Sans/license

@ovflowd
Copy link
Member Author

ovflowd commented May 3, 2025

I went ahead and got fonts from Google Fonts through this Web Helper: https://gwfh.mranftl.com/fonts

@github-actions
Copy link
Contributor

github-actions bot commented May 3, 2025

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🟢 99 🟢 100 🟢 100 🟢 91 🔗
/en/about 🟢 100 🟢 100 🟢 100 🟢 91 🔗
/en/about/previous-releases 🟢 99 🟢 100 🟢 100 🟠 83 🔗
/en/download 🟢 99 🟢 100 🟢 100 🟢 91 🔗
/en/blog 🟢 100 🟢 100 🟢 96 🟢 92 🔗

Copy link
Member

@avivkeller avivkeller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why them being on a GitHub repository doesn't mean it came from an official source? All these fonts have very permissive licenses, so you can pretty much obtain them from anywhere. https://fonts.google.com/specimen/Open+Sans/license

There's nothing wrong with use a GitHub repository. "Official" wasn't the right terminology. I meant "trusted". When you said you got the fronts from "some random GitHub repositories", it didn't seem like I could trust that the fonts used are the best / safest (although, what's unsafe about a font?) available.

Now that you've linked the source of the fonts, I'm happy to approve this PR knowing they are coming from a trusted source :-).

@ovflowd
Copy link
Member Author

ovflowd commented May 3, 2025

Why them being on a GitHub repository doesn't mean it came from an official source? All these fonts have very permissive licenses, so you can pretty much obtain them from anywhere. https://fonts.google.com/specimen/Open+Sans/license

There's nothing wrong with use a GitHub repository. "Official" wasn't the right terminology. I meant "trusted". When you said you got the fronts from "some random GitHub repositories", it didn't seem like I could trust that the fonts used are the best / safest (although, what's unsafe about a font?) available.

Now that you've linked the source of the fonts, I'm happy to approve this PR knowing they are coming from a trusted source :-).

I find the logic of blocking the PR first asking later (and possibly assuming that I wouldn't be auditing/reviewing the files/sources) a bit shocking. I'd hoped y'all trusted me more.

@avivkeller
Copy link
Member

I find the logic of blocking the PR first asking later (and possibly assuming that I wouldn't be auditing/reviewing the files/sources) a bit shocking. I'd hoped y'all trusted me more.

I'm not saying I don’t trust you. The block was simply a way of expressing that I don’t approve the landing until certain conditions (like XYZ) are met.

Also, I didn’t block first and ask questions later—I had already requested the sources to be linked, and the response I received led me to make the decision to block.

@ovflowd
Copy link
Member Author

ovflowd commented May 3, 2025

I find the logic of blocking the PR first asking later (and possibly assuming that I wouldn't be auditing/reviewing the files/sources) a bit shocking. I'd hoped y'all trusted me more.

I'm not saying I don’t trust you. The block was simply a way of expressing that I don’t approve the landing until certain conditions (like XYZ) are met.

Also, I didn’t block first and ask questions later—I had already requested the sources to be linked, and the response I received led me to make the decision to block.

I disagree with that interpretation of the events; I was clearly (or at least I thought so) joking and trying to make a lighthearted fun out of it; Apologies if that was not appropriate or direct enough.

It is your right to block a PR, but the insinuation of the sources... That's what made me uncomfortable.

I hope the PR is in a mergeable position for you now.

@avivkeller
Copy link
Member

It's in a mergeable position now. I didn't mean to make you uncomfortable, I just wanted to be safe. We both have good intentions at heart :)

@ovflowd
Copy link
Member Author

ovflowd commented May 3, 2025

It's in a mergeable position now. I didn't mean to make you uncomfortable, I just wanted to be safe. We both have good intentions at heart :)

I know, but I wanted you to understand my position, a tad over dramatic, yes.

@ovflowd
Copy link
Member Author

ovflowd commented May 3, 2025

Requesting fast-track, react with a 👍 if you approve.

@avivkeller avivkeller added this pull request to the merge queue May 3, 2025
Merged via the queue into main with commit 54bcc86 May 3, 2025
16 checks passed
@avivkeller avivkeller deleted the chore/local-fonts-console-log branch May 3, 2025 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants