nntrivi2001
9c573f1e3c
Decisions, environment quirks and pitfalls learned while working on AgentHub (docs/claude-memory/, indexed by MEMORY.md). Notes holding personal account details are left out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.5 KiB
name, description, metadata
| name | description | metadata | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| fast-bump-release | Bump + release must be quick — no full test suites at release time; run only the tests for what changed |
|
When the user asks to bump/push/release AgentHub, do it fast: bump version (package.json, package-lock.json lines 3+9, screens snapshot "UI build vX"), commit --no-verify, tag, push, forge release (EN then VI, see agenthub-release-state). Do NOT rerun both full suites at release time — the related tests already ran during the fix.
Why: 2026-10-10 the user said bump/release takes too long because of excessive testing (full server+client runs ~5–10 min, plus the pre-commit hook's full run that fails on 6–7 pre-existing tests).
How to apply: at release, at most rerun the test files touched by the change set if they were edited after their last run; never the full suites unless the user asks or the change set is large/unverified.
Exception — always run the real build gate: before tagging, run cd client && node_modules/.bin/tsc -b (exactly what npm run build runs; it type-checks TEST files too). v2.7.0 (2026-10-10) shipped a test missing required props: vitest and tsc --noEmit -p . were green, tsc -b failed, and every user's update stopped at "npm run build failed" → hotfix v2.7.1. Fast release still means skipping the full suites, never skipping tsc -b.