Files
gstack/changelog.d
Garry Tanandcapy-ai[bot] be7393888f Nightly Windows tests fit their time limit again (GST-2827) (#4409)
* Nightly Windows tests fit their time limit again (GST-2827)

The Windows duration seed missed 95 of 902 files, so the planner packed
them blind and one shard got about 26 minutes of work. Refresh the seed
from the 2026-11-16 recording and run eight shards of about 12 minutes.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Docs say the nightly Windows run uses eight shards (GST-2827)

CONTRIBUTING.md and docs/support-tiers.md still said six shards after the workflow moved to eight.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
2026-11-17 08:25:01 +00:00
..

CHANGELOG fragments

A PR adds its CHANGELOG entry here as changelog.d/<branch-slug>.md: the entry text only, with no ## [x] heading, and bump: minor or bump: major front matter only when the change warrants more than a patch, and important: security|regression|data-loss|blocker only when it must reach stable within about a day (docs/releases.md#the-daily-check). It never edits VERSION, package.json's version or a released CHANGELOG section. The merge step (gstack-ship-queue land, or train land in a stamped train) assigns the version (under merge: direct, the release PR from gstack-release-stamp open does), folds every fragment into one CHANGELOG section and deletes the files. This README is skipped. See docs/ship-policy.md#changelog-fragments.