Skip to content

Conversation

@WTW0313
Copy link
Contributor

@WTW0313 WTW0313 commented Jul 21, 2025

…il header and item> [!IMPORTANT]

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Screenshots

Before After
... ...

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

@dosubot dosubot bot added size:XXL This PR changes 1000+ lines, ignoring generated files. 💪 enhancement New feature or request labels Jul 21, 2025
@RockChinQ RockChinQ force-pushed the feat/plugin-deprecation-notice branch from fae58b2 to 35951a7 Compare July 21, 2025 08:00
@RockChinQ RockChinQ merged commit b0fc4a5 into feat/plugin-deprecation-notice Jul 21, 2025
@RockChinQ RockChinQ deleted the feat/deprecation-notice branch July 21, 2025 08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

💪 enhancement New feature or request size:XXL This PR changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants