faker
faker copied to clipboard
docs: blog post v9.0
WIP
Preview:
- https://deploy-preview-3056.fakerjs.dev/about/announcements/2024-08-31.html
- https://deploy-preview-3056.fakerjs.dev/guide/upgrading.html
Deploy Preview for fakerjs ready!
| Name | Link |
|---|---|
| Latest commit | b437755b62427c6725e1386732993ff36bfa795f |
| Latest deploy log | https://app.netlify.com/sites/fakerjs/deploys/671ced0fd09a600008a8579f |
| Deploy Preview | https://deploy-preview-3056.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.
You need to add a link here https://github.com/faker-js/faker/blob/0fd0402aa96818c8c3af1defc816ffcffadbb1fe/docs/.vitepress/config.ts#L62-L65
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 99.96%. Comparing base (
af1dbcd) to head (b437755). Report is 1 commits behind head on next.
Additional details and impacted files
@@ Coverage Diff @@
## next #3056 +/- ##
==========================================
- Coverage 99.96% 99.96% -0.01%
==========================================
Files 2804 2804
Lines 216974 216974
Branches 582 956 +374
==========================================
- Hits 216903 216892 -11
- Misses 71 82 +11
Anything else missing for this?
(We should probably rename the file to match the current date, but otherwise I think it is good to go)
also I prefer
'over’
Fixed
we should rename the file before merging, because once it is merged and public, it could be referenced by blogs like dev.to or medium
I think we should merge this and then start the release process for v9.1.