You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The build and deployment are done every midnight because the https://jc-verse.github.io/mdn-graph/warnings is supposed to show the latest issues, right?
Doing builds from the content repo is not using the latest yari code. Yari doesn't release to npmjs.com that often, so the fixes done in Yari don't reflect in builds done from content. For example, a redirect fix done in Yari won't reflect on mdn-graph/warnings till Yari does the npm release.
In the daily build and deploy workflow, it would be better to check out mdn/yari, update the .env file to point to the content repo, and then build from Yari directory using the yarn build command. And also show yari commit in the top left info panel.
The text was updated successfully, but these errors were encountered:
The build and deployment are done every midnight because the https://jc-verse.github.io/mdn-graph/warnings is supposed to show the latest issues, right?
Doing builds from the content repo is not using the latest yari code. Yari doesn't release to npmjs.com that often, so the fixes done in Yari don't reflect in builds done from content. For example, a redirect fix done in Yari won't reflect on mdn-graph/warnings till Yari does the npm release.
In the daily build and deploy workflow, it would be better to check out
mdn/yari
, update the .env file to point to the content repo, and then build from Yari directory using theyarn build
command. And also show yari commit in the top left info panel.The text was updated successfully, but these errors were encountered: