chore: release v1.36.1#295
Merged
Merged
Conversation
The aimock-cli config-fields prose lists all four llm timing fields (latency, chunkSize, replaySpeed, logLevel), but the JSON example omitted replaySpeed while showing its siblings. Add it so the example matches the documented field set.
### Fixed
- aimock.json now honours llm.latency, llm.chunkSize, llm.replaySpeed and
llm.logLevel, which the config loader previously accepted and ignored. Each
behaves as its llmock CLI flag and createMockSuite({ llm }) equivalent.
A non-positive llm.replaySpeed is ignored with a warning, matching the
existing fixture-level guard (#294)
commit: |
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.
Release v1.36.1 (patch)
Cuts a patch release for the
llmconfig passthrough fix merged in #294.Version bump
package.json1.36.0→1.36.1. (Matches this repo's practiced release convention: onlypackage.json+CHANGELOG.mdare version-carrying for aimock —charts/aimock/Chart.yaml,.claude-plugin/*, andsrc/cli.tsare not bumped per release here, as v1.36.0 also demonstrated, and no CI parity check enforces them.)CHANGELOG
Rolled the existing
[Unreleased]entry into## [1.36.1] - 2026-07-14:Docs completeness audit
Checked every place the
llmconfig is described:docs/aimock-cli/index.html— Config Fields prose rowdocs/aimock-cli/index.html—aimock.jsonJSON examplelatency,chunkSize,logLevel; missingreplaySpeed"replaySpeed": 1so the example matches the documented field setsrc/config-loader.ts—AimockConfig.llmtypedocs/index.htmllanding exampleprovidersarray, stale banner), not a field referencedocs/chat-completions/index.html,packages/aimock-pytest/README.md,README.mdllmfield referenceNet: one real gap fixed (JSON example ↔ prose consistency on the canonical config-reference page); everywhere else was already complete or is deliberately illustrative.
Quality gate
pnpm run format:check— pass (changed files clean; only a gitignored.impeccable/hook.cache.jsonlocal artifact warns)pnpm run lint— passpnpm test— 4364 passed (147 files)pnpm run build— passDraft until you're ready to merge; merging to
maintriggerspublish-release.yml(npm publish + tag + GitHub Release + Slack).