langgenius/dify-docs
1
0
Fork 0
mirror of https://github.com/langgenius/dify-docs.git synced 2026-07-22 04:15:24 -04:00
Code Issues 10 Packages Projects Releases Wiki Activity

[PR #436] [MERGED] docs: update Node.js and package manager requirements in contribution guides #504

New Issue
Closed
opened 2026-02-16 06:15:41 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 06:15:41 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-docs/pull/436
Author: @lyzno1
Created: 8/25/2025
Status: ✅ Merged
Merged: 10/21/2025
Merged by: @crazywoola

Base: main ← Head: fix/update-contribution-docs-versions

📝 Commits (1)

  • 46dd8e2 docs: update Node.js and package manager requirements in contribution guides

📊 Changes

3 files changed (+7 additions, -7 deletions)

View changed files

📝 en/community/contribution.mdx (+2 -2)
📝 ja-jp/community/contribution.mdx (+3 -3)
📝 zh-hans/community/contribution.mdx (+2 -2)

📄 Description

Summary

  • Updated Node.js version requirement from v18.x to v22.x or higher across all language versions (English, Chinese, Japanese)
  • Changed package manager requirement from npm/yarn to pnpm v10.x to match actual frontend requirements
  • Standardized Python version to 3.11.x across all language versions

Problem

The contribution documentation was outdated and inconsistent with the actual project requirements:

  • Documentation specified Node.js v18.x, but frontend README requires >= v22.11.x
  • Documentation mentioned npm/yarn, but project actually uses pnpm v10.x
  • Japanese version had inconsistent Python version (3.10.x vs 3.11.x)

Solution

Updated all three language versions of the contribution guide to match the actual project requirements, preventing setup issues for new contributors.

Test plan

  • Verified changes match actual frontend README requirements
  • Ensured consistency across all language versions
  • Confirmed no other references need updating

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-docs/pull/436 **Author:** [@lyzno1](https://github.com/lyzno1) **Created:** 8/25/2025 **Status:** ✅ Merged **Merged:** 10/21/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `fix/update-contribution-docs-versions` --- ### 📝 Commits (1) - [`46dd8e2`](https://github.com/langgenius/dify-docs/commit/46dd8e2bb830a2839ee04315312be311c0736a64) docs: update Node.js and package manager requirements in contribution guides ### 📊 Changes **3 files changed** (+7 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `en/community/contribution.mdx` (+2 -2) 📝 `ja-jp/community/contribution.mdx` (+3 -3) 📝 `zh-hans/community/contribution.mdx` (+2 -2) </details> ### 📄 Description ## Summary - Updated Node.js version requirement from v18.x to v22.x or higher across all language versions (English, Chinese, Japanese) - Changed package manager requirement from npm/yarn to pnpm v10.x to match actual frontend requirements - Standardized Python version to 3.11.x across all language versions ## Problem The contribution documentation was outdated and inconsistent with the actual project requirements: - Documentation specified Node.js v18.x, but frontend README requires >= v22.11.x - Documentation mentioned npm/yarn, but project actually uses pnpm v10.x - Japanese version had inconsistent Python version (3.10.x vs 3.11.x) ## Solution Updated all three language versions of the contribution guide to match the actual project requirements, preventing setup issues for new contributors. ## Test plan - [x] Verified changes match actual frontend README requirements - [x] Ensured consistency across all language versions - [x] Confirmed no other references need updating --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 06:15:41 -05:00
yindo closed this issue 2026-02-16 06:15:41 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
documentation
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-docs#504
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?