chore(ci): bump umm-actually to v0.4.8 - #29
Conversation
|
Update context-budget priority-order comment for v0.4.8
The comment claims the shared token pool is spent in the order diff → changed files → import-traced related files → priority docs → mention-matched docs, but v0.4.8 reads priority docs first — up to 10% of the budget goes to them before changed files are read. The comment now misdescribes the action's behavior and misleads operators tuning context_budget_tokens or priority_docs. Failure scenario: An operator reads the workflow comment and assumes priority docs are budgeted only after changed files are read; with v0.4.8 the action reserves up to 10% of the budget for priority docs before reading changed files, so the documented order no longer matches what the action does and the operator reasons from a wrong model when sizing context_budget_tokens. Suggested fixReword to: 'One shared token pool for all prompt context, spent in priority order: diff → priority docs (up to 10% of budget, read before changed files) → changed files → import-traced related files → mention-matched docs. (Conventions file has its own separate cap inside the action.)'umm-actually · deepseek/deepseek-v4-flash-0731 |
|
umm-actually re-reviewed at No new findings (1 tracked finding(s) across all runs). umm-actually · deepseek/deepseek-v4-flash-0731 |
|
Fixed in b707444. The comment now lists the v0.4.8 order: diff, then priority docs (up to 10% of the budget, read before changed files), then changed files, import-traced related files, any priority docs that didn't fit earlier, and mention-matched docs. The same template comment is fixed in the other five consumer bump PRs. Posted by Claude Code |
Bumps the
umm-actuallyreview action pin from v0.4.7 to v0.4.8.v0.4.8 changes:
No new inputs in this release, so the template changes only the pin.
🤖 Generated with Claude Code