-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update dependency next-contentlayer to v0.3.4 #53
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/next-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 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 ↗︎
|
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
January 18, 2023 23:23
cdb80a5
to
e021243
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
January 30, 2023 00:10
e021243
to
70e6eab
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
January 31, 2023 06:48
70e6eab
to
15a6199
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
February 1, 2023 20:59
15a6199
to
d201277
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
February 10, 2023 19:33
d201277
to
018fcf8
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
February 12, 2023 23:36
018fcf8
to
0eaf7bd
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
February 13, 2023 19:52
0eaf7bd
to
fc9cf94
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
February 26, 2023 20:56
fc9cf94
to
ef42e21
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
March 2, 2023 21:12
ef42e21
to
af3d132
Compare
renovate
bot
changed the title
Update dependency next-contentlayer to v0.3.0
Update dependency next-contentlayer to v0.3.1
Mar 28, 2023
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
March 28, 2023 07:27
af3d132
to
3355f94
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
April 21, 2023 12:07
3355f94
to
f5ef345
Compare
renovate
bot
changed the title
Update dependency next-contentlayer to v0.3.1
Update dependency next-contentlayer to v0.3.2
Apr 25, 2023
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
April 25, 2023 03:49
f5ef345
to
b8d1b01
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
May 14, 2023 23:33
b8d1b01
to
596a4ef
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
May 22, 2023 07:24
596a4ef
to
1cba752
Compare
renovate
bot
changed the title
Update dependency next-contentlayer to v0.3.2
Update dependency next-contentlayer to v0.3.3
May 31, 2023
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
May 31, 2023 16:56
1cba752
to
74a53f3
Compare
renovate
bot
changed the title
Update dependency next-contentlayer to v0.3.3
Update dependency next-contentlayer to v0.3.4
Jun 29, 2023
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
June 29, 2023 11:54
74a53f3
to
9afb82a
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
July 19, 2023 14:47
9afb82a
to
1a549fa
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
August 19, 2023 00:07
1a549fa
to
0db2fe2
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
October 23, 2023 21:06
0db2fe2
to
37d5dc7
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
October 26, 2023 17:40
37d5dc7
to
e2937f6
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
October 26, 2023 17:44
e2937f6
to
fe69aca
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
October 26, 2023 17:50
fe69aca
to
9c8fc32
Compare
renovate
bot
force-pushed
the
renovate/next-contentlayer-0.x
branch
from
October 26, 2023 20:09
9c8fc32
to
34a07e9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.4
Release Notes
contentlayerdev/contentlayer (next-contentlayer)
v0.3.4
: 0.3.4Compare Source
ℹ️ [TLDR] Many smaller bug fixes, improvements and updated dependencies
Improvements
aspectRatio
property toImageFieldData
fortype: image
fieldsyaml
package - closes #488)Bug fixes
v0.3.3
: 0.3.3Compare Source
ℹ️ [TLDR] New onSuccess callback that runs after completing a build successfully
✨
onSuccess
CallbackA 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
body
field in frontmatter. Now, both Markdown and MDX files behave in the same way, supporting abody
field 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-contentlayer
integrationAs part of
0.3.2
we've overhauled thenext-contentlayer
integration 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
redirects
workaround) Contentlayer now also works withnext export
. (closes #426)Other Improvements
contentDirInclude
didn'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.