Add July 2026 newsletter - #3987
Merged
Merged
Conversation
…ditions Replace article counts, volume superlatives, and discovery-methodology references (derived from an internal press index) with qualitative phrasing in the April, May, and June editions, keeping only publicly verifiable data.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds the July 2026 newsletter and removes unverifiable press-volume figures from prior editions.
Changes:
- Summarizes July releases, ecosystem growth, security work, and roadmap.
- Rephrases April–June coverage metrics qualitatively.
- Contains inaccurate Python-migration and integration-growth claims requiring correction.
Show a summary per file
| File | Description |
|---|---|
newsletters/2026-April.md |
Rephrases article-volume claims. |
newsletters/2026-May.md |
Removes press-count claims. |
newsletters/2026-June.md |
Replaces coverage figures with qualitative wording. |
newsletters/2026-July.md |
Adds the July newsletter. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Suppressed comments (1)
newsletters/2026-July.md:128
- This row uses a start count that cannot produce the stated end count from July's changes. The v0.12.2 registry has 35 entries and v0.15.1 has 37, so this should report 35 → 37 and +2 net.
| Agent integrations | 34 | 37 | +3 (net) |
- Files reviewed: 4/4 changed files
- Comments generated: 2
- Review effort level: Balanced
|
|
||
| Spec Kit's second July theme was quieter but structurally important: the project began migrating its shell scripts to **Python**. The new **`py` script type** (#3285) joins `sh` (bash) and `ps` (PowerShell) as a third option at `specify init`, backed by Python-interpreter resolution that skips broken stubs (including the Windows Store `python3` alias, #3385). The `py` type is the project's answer to the perennial bash/PowerShell parity tax — every script fix previously had to be written twice and kept in sync, a recurring source of the Windows-parity bugs that filled prior months' changelogs. | ||
|
|
||
| Behind the new type, a systematic port landed piece by piece across the month: the **`update-agent-context`** updater (#3387), the **git extension scripts** (#3400), a **`check-prerequisites`** proof-of-concept (#3302), and finally the three core scripts — **`create-new-feature`, `setup-plan`, and `setup-tasks`** (#3386). The wheel was updated to bundle `scripts/python` so `--script py` works from a clean PyPI install (#3665), and the installation docs and init option table were updated to document the new type and the sh/ps migration plan (#3284, #3640). The end state is a single, cross-platform script implementation that removes an entire class of parity bugs. [\[github.com\]](https://github.com/github/spec-kit/releases) |
|
|
||
| ### Agent Integrations | ||
|
|
||
| The agent portfolio grew net **+3 to 37 integrations**. Three joined — **Grok Build** (#3535), **Factory Droid CLI** (#3587, closing the 300+-day #822), and **Alquimia AI** (#2734) — while **Roo Code** was retired as a shut-down product (#3212). **Bob** was migrated to a skills-based layout for Bob 2.0 (#3415), **Kilocode** now installs commands under `.kilo/commands` (#3672), and a broad correctness pass fixed hyphenated-command rendering and dispatch for the always-slash agents (Droid, Forge, Cline) and preserved native skill-invocation prefixes (#3663). The pattern continues from June — pruning dead products while making the surviving integrations more native to each agent. [\[github.com\]](https://github.com/github/spec-kit/releases) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds the July 2026 newsletter (
newsletters/2026-July.md), following the established monthly format.Highlights covered:
assessIdea Assessment Pipeline extension (pre-spec evaluation)pyscript type and the shell→Python portGrounding: GitHub release notes/
ghfor all release and feature facts; the public community catalog and public repo metrics for growth numbers. The end-of-July star count matches the repo's own tracking (124,655).A second commit does a small cleanup of the April, May, and June editions, replacing a handful of press-volume figures with qualitative phrasing so every edition relies only on publicly verifiable data. All links across the editions are external.
Testing
uv run specify --helpuv sync && uv run pytestDocs-only change (Markdown newsletters); no code paths affected.
AI Disclosure
Drafted with GitHub Copilot: release/feature facts gathered from GitHub and the
ghCLI, community/press items from public sources; all content reviewed and edited by the author.