-
Notifications
You must be signed in to change notification settings - Fork 0
Update dependency contentlayer to v0.3.4 #52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/contentlayer-0.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
d216e11 to
e3e407b
Compare
e3e407b to
798a4a8
Compare
798a4a8 to
052a930
Compare
052a930 to
f175e6f
Compare
f175e6f to
2c7ba38
Compare
2c7ba38 to
618939c
Compare
618939c to
a0951bd
Compare
a0951bd to
4da5cf9
Compare
4da5cf9 to
ddf5c92
Compare
ddf5c92 to
ee5fe4d
Compare
ee5fe4d to
773a8bd
Compare
773a8bd to
4bcaaa8
Compare
4bcaaa8 to
4c7f77a
Compare
4c7f77a to
3c1c292
Compare
3c1c292 to
5d141c8
Compare
5d141c8 to
f277826
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.3.1->0.3.4Release Notes
contentlayerdev/contentlayer (contentlayer)
v0.3.4: 0.3.4Compare Source
ℹ️ [TLDR] Many smaller bug fixes, improvements and updated dependencies
Improvements
aspectRatioproperty toImageFieldDatafortype: imagefieldsyamlpackage - closes #488)Bug fixes
v0.3.3: 0.3.3Compare Source
ℹ️ [TLDR] New onSuccess callback that runs after completing a build successfully
✨
onSuccessCallbackA new callback will now be called when a successful build has completed.
The callback function receives a single argument that is an asynchronous function from which you can access data objects processed and generated by Contentlayer.
Running a build with the above configuration would yield something like the following on the console.
Better Non-Latin Character Support
Support has improved for characters in non-Latin languages. Fixes #337.
🙌 Thanks to @huanfe1 for help!
Other Improvements
Here are the other improvements shipped with this version.
Fix Body Field Handling for MDX
@stefanprobst resolved the discrepancy in handling a
bodyfield in frontmatter. Now, both Markdown and MDX files behave in the same way, supporting abodyfield in the frontmatter. See #451 for details.Upgraded Dependencies
Dependencies have been upgraded to avoid warning messages. Fixes #360.
v0.3.2: 0.3.2Compare Source
ℹ️ [TLDR] Bug fixes for
next dev, Support fornext export, bug fixes and updated dependenciesImproved
next-contentlayerintegrationAs part of
0.3.2we've overhauled thenext-contentlayerintegration with the goal of making it more stable and less dependent on implementation details of Next.js. This fixes #415 and #416 (thanks @kamto7).As part of this effort (and by no longer relying on the
redirectsworkaround) Contentlayer now also works withnext export. (closes #426)Other Improvements
contentDirIncludedidn't work in some cases (closes #383 - thanks to @teobler)Note about state of the project
Please also take a look at #429 to read about the current state of the project. 💜
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.