v1.0.0 To v1.1.0
Migrate older Markdown block code parameter fields removed after v1.0.0.
v1.0.0 To v1.1.0
Summary
This release simplified code block configuration and removed legacy fields that are no longer used by the renderer.
A small schema reconciliation may be required if you previously customized code block behavior inside stored block config.
What Changed
Removed fields:
prettyCodeBlockshighlightLines
Replaced by:
enhancedCodeBlocks
enhancedCodeBlocks is now also a deprecated config alias in the newer public API. For current plugin configuration, prefer:
1payloadMarkdown({2 code: {3 enhanced: true,4 },5})
Who Is Affected
You are only affected if:
- you customized Markdown block config, and
- you used
prettyCodeBlocksorhighlightLines
If you did not modify code block settings, no action is required.
Migration Steps
1 Back Up Data
Back up production data before applying schema migrations or accepting field reconciliation prompts.
2 Test Locally
Run the app in development mode against a local or backup database.
3 Open A Markdown Block
Open a page or post that uses Markdown block config.
4 Reconcile If Prompted
If Payload prompts you to reconcile fields, replace
prettyCodeBlockswithenhancedCodeBlocksand removehighlightLines.5 Repeat
Repeat for additional instances if Payload reports more stored block configs.
Result
After completing these steps:
- your schema is aligned with v1.1.0
- code block rendering behaves as expected
- legacy removed fields are gone from stored block config
Newer Config Migration
For current plugin configuration, migrate from config.options to top-level or collection-level code:
1payloadMarkdown({2 code: {3 enhanced: true,4 lineNumbers: true,5 shikiTheme: 'github-dark',6 },7})