`CreateUpdate.ts --help` does not list `--upgrade-id`
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 95/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bun, typescript
- Domain
- cli
Research direction
Start in LifeOS/install/LIFEOS/TOOLS/CreateUpdate.ts, reading the help block at lines 520-538 and the existing --upgrade-id parsing and usage around lines 514, 594, and 644-667. Run the provided Bun --help and grep commands on a clean tree. Done means the help output lists --upgrade-id while the existing parsing and behavior remain intact.
Written by the indexing model from the issue text.
Description
Version
LifeOS 7.40.4 / Ledger
What is broken
CreateUpdate.ts accepts and uses --upgrade-id, the flag that joins an Upgrades-queue item to its Ledger entry, but the --help output never mentions it.
Where (file:line)
parsed at LifeOS/install/LIFEOS/TOOLS/CreateUpdate.ts:514,594 and used at :644,663-667. The help block is at :520-538.
Repro on a clean tree
H=$(mktemp -d); HOME=$H bun LifeOS/install/LIFEOS/TOOLS/CreateUpdate.ts --help | grep -c -- '--upgrade-id'
rg -n 'upgrade-id' LifeOS/install/LIFEOS/TOOLS/CreateUpdate.ts
Negative control
On unpatched 7.40.4 the help output contains --upgrade-id 0 times, while the source parses it at lines 514 and 594.
Suggested fix
Add one help line, for example --upgrade-id <id> link this update to an Upgrades queue item.
Before submitting
- I searched open and closed issues for this defect.
- The repro runs against a clean tree of the version above, not against my modified install.
- I removed personal data from the pasted output — real names, absolute home paths, tokens, my own content.
- Dominant language
- TypeScript
- Stars
- 19.2k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from danielmiessler/LifeOS
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
danielmiessler/LifeOS#2262 ·
Maintainers usually reply within 4 days
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
danielmiessler/LifeOS#2261 · 1 comment ·
Maintainers usually reply within 4 days
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
danielmiessler/LifeOS#2260 ·
Maintainers usually reply within 4 days
-
v7.40.4: `lifeos -s <missing file>` launches Claude without the constitution and without any warningOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
danielmiessler/LifeOS#2255 · 1 comment ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
danielmiessler/LifeOS#2251 ·
Maintainers usually reply within 4 days
All issues in danielmiessler/LifeOS
Similar issues
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pingdotgg/t3code#14452 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
solana-foundation/program-examples#747 · 1 comment ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
remotion-dev/remotion#11847 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openwatersio/slackwater#355 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melgarafael/DeskcommCRM#1998 · 3 comments ·
Maintainers usually reply within 1 day