chore(release): v0.16.5 - #218
Merged
Merged
Conversation
`moshcode update` now checks before it installs. moshcode update --check is there a newer release? moshcode update --if-newer install only if there is moshcode update --timer [--install] check on a schedule, 15min default Until now every run re-fetched Node, bun and the release tarball whether or not anything had changed — fine as a thing you type, wrong as a thing a timer runs every fifteen minutes. Versions compare in order rather than by string inequality, so a rolled back release does not read as an upgrade and 0.9.0 does not read as newer than 0.10.0. An unreachable feed means do nothing, because a timer that reinstalls on every failed check hammers a machine that is merely offline. The timer sets Persistent=true so a sleeping laptop checks on waking, and runs the checking form rather than a bare update. Automatic updates hand a bad release to every machine on the timer within the interval, with nobody in the loop — which is worth knowing before enabling the installing form rather than the checking one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releases the check-before-install work from #217 — slightly circular otherwise, since you'd need to upgrade to get the thing that decides whether to upgrade.
Until now every run re-fetched Node, bun and the release tarball whether or not anything changed.
Ordered version compare, so a rolled-back release isn't an upgrade and
0.9.0isn't newer than0.10.0. Unreachable feed means do nothing, because a timer that reinstalls on every failed check hammers a machine that's merely offline.Persistent=trueso a sleeping laptop checks on waking. The unit runs--if-newer, not bareupdate— tested, because that mistake turns a 15-minute timer into a 15-minute reinstall.Automatic updates hand a bad release to every machine on the timer within the interval, with nobody in the loop. Worth knowing before enabling the installing form rather than the checking one.
🤖 Generated with Claude Code