[PR #369] docs: record DeepSeek V4 release versions #375

New issue

Open

opened 2026-10-26 09:48:34 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-26 09:48:34 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/deepseek-ai/awesome-deepseek-agent/pull/369
Author: @morluto
Created: 8/12/2026
Status: 🔄 Open

Base: main ← Head: agent/document-v4-release-versions

📝 Commits (1)

3ad56e6 docs: record DeepSeek V4 release versions

📊 Changes

3 files changed (+20 additions, -0 deletions)

View changed files

📝 CONTRIBUTING.md (+2 -0)
📝 README.md (+9 -0)
📝 README.zh-CN.md (+9 -0)

📄 Description

Summary

Add the release-version mapping for deepseek-v4-flash and deepseek-v4-pro to both README files.
Add the same mapping to the contributor model-naming guidance.
Keep the callable API IDs in configuration examples and document the release strings as identification metadata.

The mapping is:

API model ID	Release version
`deepseek-v4-flash`	`DeepSeek-V4-Flash-0731`
`deepseek-v4-pro`	`DeepSeek-V4-Pro-0813`

Validation

git diff --check
npx --yes markdownlint-cli --disable MD001 MD013 MD041 MD060 -- README.md README.zh-CN.md CONTRIBUTING.md

The Markdown lint command reports pre-existing errors for the repository's HTML-wrapped READMEs, multiple blank lines, and an unlabeled code fence in CONTRIBUTING.md; it reports no new issue in the added sections.

The API model IDs remain aligned with DeepSeek's model list: https://api-docs.deepseek.com/api/list-models

_{🔄 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/deepseek-ai/awesome-deepseek-agent/pull/369 **Author:** [@morluto](https://github.com/morluto) **Created:** 8/12/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `agent/document-v4-release-versions` --- ### 📝 Commits (1) - [`3ad56e6`](https://github.com/deepseek-ai/awesome-deepseek-agent/commit/3ad56e670cb5200f39a7366cab31522672cb5503) docs: record DeepSeek V4 release versions ### 📊 Changes **3 files changed** (+20 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `CONTRIBUTING.md` (+2 -0) 📝 `README.md` (+9 -0) 📝 `README.zh-CN.md` (+9 -0) </details> ### 📄 Description ## Summary - Add the release-version mapping for `deepseek-v4-flash` and `deepseek-v4-pro` to both README files. - Add the same mapping to the contributor model-naming guidance. - Keep the callable API IDs in configuration examples and document the release strings as identification metadata. The mapping is: | API model ID | Release version | | ------------ | --------------- | | `deepseek-v4-flash` | `DeepSeek-V4-Flash-0731` | | `deepseek-v4-pro` | `DeepSeek-V4-Pro-0813` | ## Validation - `git diff --check` - `npx --yes markdownlint-cli --disable MD001 MD013 MD041 MD060 -- README.md README.zh-CN.md CONTRIBUTING.md` The Markdown lint command reports pre-existing errors for the repository's HTML-wrapped READMEs, multiple blank lines, and an unlabeled code fence in `CONTRIBUTING.md`; it reports no new issue in the added sections. The API model IDs remain aligned with DeepSeek's model list: https://api-docs.deepseek.com/api/list-models --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

2026-10-26 09:48:34 +00:00

bsakaguchi referenced this issue

2026-10-26 09:48:37 +00:00

[PR #375] [CLOSED] docs: expand Hermes guide — Windows install, model selection, real-world usage #380