[goosewobbler]

Description

Biome's suspicious/noExplicitAny goes from a warning to an error for all .ts files. Specs (**/*.spec.ts) and **/mocks/*.ts keep it off, as before. This is the same move as #679 for braces: a convention that was only prose (it was in #673's AGENTS.md draft) is now enforced, so #673 drops the line.

There were exactly three warnings, all in source:

Site	Change
notes/src/llm/openai.ts schema: options.schema as any	Cast removed. options.schema is JSONSchema, which is already Record<string, unknown>, the type the SDK's json_schema.schema takes.
publish/src/stages/verify.ts (crates.io and pub.dev) (error as any).fatal	'fatal' in error && error.fatal, which narrows without a cast and keeps the same truthiness check.

No behaviour changes.

Related Issue(s)

None. Follows the review of #673, where the "avoid any" line was better enforced than written down.

Type of Change

• feat — New feature
• fix — Bug fix
• docs — Documentation change
• refactor — Code refactoring
• test — Adding or updating tests
• chore — Maintenance, dependencies, tooling
• Breaking change — Requires major version bump

Scope

• @releasekit/version
• @releasekit/notes
• @releasekit/publish
• @releasekit/release
• @releasekit/config
• @releasekit/core
• CI / workflows
• Root / monorepo

Checklist

• Lint passes (pnpm lint)
• Tests pass (pnpm test)
• Typecheck passes (pnpm typecheck)
• Documentation updated (if applicable)
• Breaking changes noted in description

Testing Notes

• pnpm build, pnpm lint and pnpm typecheck pass. Lint reports 26 warnings, down from 29 on main: the three noExplicitAny warnings are gone.
• The rule fires: a temporary packages/core/src file with (x: any) => x fails biome lint with lint/suspicious/noExplicitAny, and a temporary spec using any doesn't. Both were removed afterwards.
• @releasekit/notes and @releasekit/publish tests pass. The verify change is covered by the two "should fail fast on 403" tests. Inverting the new check fails both, so they exercise it.
• The open PRs (feat(cli)!: envelope the version and publish commands, unwrap on the pipe #616, test(notes): add the structured enhance-and-categorize eval case #617, test(notes): make the LLM e2e infra-tolerant and close a false green #618, chore(biome): flag console in package source #668, ci: skip CodeQL, release preview and title checks on the standing release PR #672, fix(version)!: sync every committed Cargo.lock that records a bumped crate #674, docs: document the standing-PR body as an interface, add agent guidance #619) add no any outside specs and mocks, so none of them will fail on this rule after it merges.

---

Generated by Claude Code

Confidence Score: 5/5

The PR appears safe to merge; no actionable issues were found.

Summary

Makes noExplicitAny an error in TypeScript source.

• TypeScript linting now rejects explicit any outside specs and mocks.

No actionable issues found. Tests and builds were not run during this review.

_{Reviews (1) · Last reviewed commit: "chore(biome): make noExplicitAny an erro..." · Reviewed by Greptile}

[github-actions]

Standing release PR: #614 · v0.42.0 queued (4 packages) · open 82d 1h 22m · ✅ ready to merge

Release Preview — v0.41.2 → v0.41.3

Note: Labels on this PR are advisory in standing-pr mode. Bumps come from conventional commits in the standing PR; override by editing labels on the standing PR itself. Add release:immediate to bypass the standing PR and release this PR directly.

These changes will be added to the release PR (#614) when merged:

Changelog

monorepo 0.41.2 → 0.41.3

Changed

• make noExplicitAny an error outside specs and mocks (biome)

All packages → 0.41.3 (sync versioning)

• @releasekit/version
• @releasekit/notes
• @releasekit/publish
• @releasekit/release

After merge — predicted release

No version escalation — this PR's changes will be included in the queued release without affecting the projected versions.

Package	Standing PR	This PR	After merge
monorepo	0.42.0	0.41.3	0.42.0

---

Updated automatically by ReleaseKit