feat: update netlify-plugin-ghost-markdown to v3.1.0

[daviddarnes]

Are you adding a plugin or updating one?

• Adding a plugin
• Updating a plugin

Have you completed the following?

• Read and followed the plugin author guidelines.
• Included all required fields in your entry.
• Tested the plugin locally and on Netlify, using the plugin version stated in your entry.

Test plan
Please add a link to a successful public deploy log using the stated version of the plugin. Include any other context reviewers might need for testing. https://app.netlify.com/sites/netlify-plugin-ghost-markdown-demo/deploys/630490577d2b184655b30fa6

Ps. Has the local development workflow improved for Build Plugins? I currently have an additional repo which is connected to a Netlify site just to test my plugin locally. Ideally I'd have a test / demo directory in my Build Plugin repo which I can test with and demonstrate the plugin. Can anyone give me any pointers? Thanks!

[netlify-bot]

Updated Packages

• https://diff.intrinsic.com/netlify-plugin-ghost-markdown/3.0.3/3.1.0

[ericapisani]

Hi @daviddarnes ,

Thanks for submitting a pull request!

Regarding your question about the local development workflow - I think you might be interested in taking a peek (if you haven't already) at Netlify's Next.js Runtime repo for an example that includes demo sites that are used for testing and demonstrating various use cases (the default one can be found here).

Let me know if that's what you had in mind or if you have any follow up questions about that (though if we have a more extended back and forth, happy to move the conversation into an issue on your plugin's repository)

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[daviddarnes]

Thanks very much @ericapisani! I’ll take a look at that repo. I think the dev workflow has improved since I first made it so hopefully I can tighten things up into a single repo and single site demo.

Ps. Thanks for merging the update!