Skip to content

release: clean fduty self-update logs -> main (cut v0.0.25)#76

Merged
ysyneu merged 2 commits into
mainfrom
feat/ai-sre
Jun 15, 2026
Merged

release: clean fduty self-update logs -> main (cut v0.0.25)#76
ysyneu merged 2 commits into
mainfrom
feat/ai-sre

Conversation

@ysyneu

@ysyneu ysyneu commented Jun 15, 2026

Copy link
Copy Markdown
Collaborator

Promotes the fduty self-update logging cleanup (#75) to main for a patch release v0.0.25.

Net change since v0.0.24: fduty self-update now emits clean, single-line, definitive log lines (fduty CLI upgraded from=… to=… / already up to date / single-line error) instead of raw truncated multi-line output that showed literal \n and cut off mid-string. See #75 for before/after and test evidence.

ysyneu added 2 commits June 15, 2026 19:57
The success path logged head(out,300) of `fduty update`'s raw multi-line
output, which surfaced in logs as literal `\n` escapes truncated mid-string
(a colleague reported messy/cut-off logs). Replace it with single-line,
definitive logging:

- verifyFdutyOnPath now returns the resolved version line; ensureFdutyCLI
  passes the pre-update version into fdutySelfUpdate(prevVersion).
- after a successful `fduty update`, re-read the version and log the actual
  outcome: "fduty CLI upgraded" from->to, or "already up to date".
- the failure path logs the last output line (the real error) via lastLine
  instead of a truncated head.
- firstLine/lastLine helpers replace the head() byte-truncator.
fix(provision): clean, definitive fduty self-update logs
@ysyneu ysyneu merged commit 0dd5162 into main Jun 15, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant