Model Releases and Developer Tool Updates #27

Today's Letter

1. DeepSeek, V4 Preview models and 1M context released
2. GitHub npm staged publishing GA, new install source controls

DeepSeek, V4 Preview models and 1M context released

• DeepSeek published the DeepSeek-V4 Preview on April 24, 2026, with API availability and open weights announced on the official API docs site
• The release includes DeepSeek-V4-Pro with 1.6T total parameters and 49B active parameters, and DeepSeek-V4-Flash with 284B total and 13B active parameters
• DeepSeek said both models support a 1M-token context window by default across official services, with Thinking and Non-Thinking modes available
• The API keeps the same base URL and only requires switching the model name to `deepseek-v4-pro` or `deepseek-v4-flash`
• DeepSeek said the models support both OpenAI Chat Completions and Anthropic API compatibility paths
• The company described a new attention design based on token-wise compression and DeepSeek Sparse Attention for lower long-context compute and memory cost
• DeepSeek also said V4 is integrated with agent tools including Claude Code and is already used for in-house agentic coding workflows
• DeepSeek said `deepseek-chat` and `deepseek-reasoner` will be fully retired after July 24, 2026, 15:59 UTC, with current traffic routed to V4-Flash modes

Source: api-docs.deepseek.com
More: github.com · news.hada.io · businessnewsthisweek.com

GitHub npm staged publishing GA, new install source controls

• GitHub released two npm supply-chain security updates on May 22, 2026: staged publishing GA and new install-time source controls.
• Both features require npm CLI 11.15.0 or newer.
• Staged publishing uploads a prebuilt tarball to a stage queue instead of making a package version immediately installable.
• A maintainer must explicitly approve the staged package with a 2FA challenge before release to the npm registry.
• The stage queue is visible on npmjs.com and in the npm CLI.
• GitHub said the flow reinforces proof of presence for every publish, including CI/CD and trusted publishing with OIDC.
• GitHub recommends replacing npm publish with npm stage publish in CI workflows where staged release behavior is required.
• npm 11.15.0 also adds --allow-file, --allow-remote, and --allow-directory, extending the existing --allow-git control to all non-registry install sources.
• Each flag accepts all or none, can be set in .npmrc or package.json config, and --allow-git is still scheduled to change its default from all to none in v12.

Source: github.blog

Jocoletter curates AI, software, and product trends for developers and builders.

#DeepSeek #GitHub

Subscribe to Jocoletter