fix : add patch for {docsify-ignore} and {docsify-ignore-all}

[sy-records]

Summary

<!-- {docsify-ignore} --> is a major change and should be put into v5.

But a version has already been released, so a patch version has been added that is compatible with older versions and can be removed in v5.

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Docs
• Build-related changes
• Repo settings
• Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

• Chrome
• Firefox
• Safari
• Edge
• IE

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature
• Related documents have been updated
• Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/docsify-core/docsify-preview/kquxak60d
✅ Preview: https://docsify-preview-git-fork-sy-records-reset-1318.docsify-core.vercel.app

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 204bfbb:

Sandbox	Source
docsify-template	Configuration

[Koooooo-7]

I think we should keep the <!-- {docsify-ignore} --> and also let the {docsify-ignore} work fine, in case of causing the second breaking for users who may already use the new option.

[anikethsaha]

I agree with @Koooooo-7 if we can manage to to ship the changes it would be great.
Though I will not wait too much cause we need to do the patch release soon

[sy-records]

@anikethsaha @Koooooo-7 Done.

In #1318, I had a reference to the need for compatibility. #1318 (review)

[Koooooo-7]

TODO: when and how we will solve it.

[sy-records]

TODO: when and how we will solve it.

Awaiting @trusktr and @jhildenbiddle approval, release v4.11.6

[trusktr]

LGTM. For later, we can revert the PR merge commit to re-create these changes. We can open a PR with the changes, and just keep it open for v5 until we're ready.

[trusktr]

Should we revert the removal of src from publish, then remove it as a breaking change for v5? Thoughts @jhildenbiddle?

[sy-records]

Should we revert the removal of src from publish, then remove it as a breaking change for v5? Thoughts @jhildenbiddle?

#1343 (comment)

[trusktr]

Thanks for doing this! This is good, to keep both forms.

[trusktr]

Oops. Looks good! Let's get this in.

[sy-records]

@trusktr Do we have to wait for @jhildenbiddle ? Or can we merge and release patch versions now?