Skip to content

fix(deps): update dependencies - #24

Open
tannevaled wants to merge 1 commit into
mainfrom
renovate/deps
Open

tannevaled wants to merge 1 commit into
mainfrom
renovate/deps

Conversation

@tannevaled

@tannevaled tannevaled commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
github.com/go-fleettools/fleettools v0.72.0 → v0.140.0 age confidence
github.com/go-gitsafe/gitsafe v0.49.0 → v0.56.2 age confidence

Release Notes

go-fleettools/fleettools (github.com/go-fleettools/fleettools)

v0.140.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.139.0...v0.140.0

v0.139.0

Compare Source

What's Changed

  • recur --hook: refuse the owner at once, everyone else after a grace period by @​tannevaled in #​359

Full Changelog: go-fleettools/fleettools@v0.138.0...v0.139.0

v0.138.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.137.0...v0.138.0

v0.137.0

Compare Source

What's Changed

  • acdefault: read "(default is yes)", the third spelling this refused a real tree over by @​tannevaled in #​353
  • binnames: refuse an installed binary that shares its name with a well-known command by @​tannevaled in #​356

Full Changelog: go-fleettools/fleettools@v0.136.0...v0.137.0

v0.136.0

Compare Source

What's Changed

  • diffrefs: the references a DIFF adds, with the ones that do not exist yet refused by @​tannevaled in #​349
  • diffrefs: say that it cannot be run after the fact, and how to run it before a tag exists by @​tannevaled in #​351
  • acdefault: say N OF M, because "3 switch(es) examined" was six per cent reported as a census by @​tannevaled in #​352

Full Changelog: go-fleettools/fleettools@v0.135.0...v0.136.0

v0.135.0

Compare Source

What's Changed

  • acdefault: what an autotools switch really defaults to, read from the generated configure by @​tannevaled in #​347
  • ghissue: --comment edits an existing comment, the one tracker write with no program left by @​tannevaled in #​348
  • ghrepo: add private-reporting enable|disable|status by @​tannevaled in #​350

Full Changelog: go-fleettools/fleettools@v0.134.0...v0.135.0

v0.134.0

Compare Source

Two commits since v0.133.0, and they are the two halves of one afternoon: a question three sessions could not answer, and the reason none of them noticed the answer was already half-written.

New: cmd/testtime (#​345)

Which tests account for a package's wall clock, from go test -json:

go test -json ./... | testtime
testtime run.json --top 12 --subtests

It refuses the two arithmetic errors that make such a report lie. A parent's Elapsed already contains its subtests, so only top-level names are totalled and --subtests answers the other question in its own column. And parallel tests overlap, so when their sum exceeds the package's own elapsed it prints PARALLEL instead of a share — a percentage of a clock several tests occupied at once is a fraction of nothing. It reports and does not judge: no threshold, no "too slow". Exit 2 on input holding no test events, so a report over nothing cannot look like a clean one.

⚠ The gap it fills is narrower than the claim that motivated it. That commit's message says the fleet's existing tools read no elapsed times; cmd/testwhy does, per PACKAGE, and uses -min-seconds as a witness that a package which finished implausibly fast ran nothing. What nobody had is the breakdown within a package, which is what testtime adds. The correction is in testtime's own doc comment and the README row; the commit message is immutable and carries the earlier wording.

cmd/fleetverbs: a zero from --match says what it did not search (#​346)

--match reads names and documentation. Printed alone, its zero reads as "nothing here does X" — and that is exactly how it was read on 2026-11-17, three times by one session and nearly a fourth by another:

fleetverbs --match elapsed --cli .
  113 package(s), 203 file(s): 0 exported symbol(s), 0 verb(s)

…while cmd/testwhy was in that very tree, reading elapsed times. --text finds it; --match cannot, because a capability reached through a table or a doc line that never spells the word has no symbol named for it. The zero now carries its own surface and names the flag that widens it.

This is the rule the command already followed for what it could not read — every unparseable file, skipped fixture and missing path is counted and named — extended to the case where everything was read and the search was narrow. priorart has always answered this way about its own surfaces ("2 surface(s) could not be read; that is not an absence of prior art").

⭐ What exposed it was a positive control, not care: --match ledger, a word certainly in cmd/recur, also answered 0. Three repetitions of a narrow search are one measurement.

The shape worth keeping from both

A tool whose search surface is narrower than its subject reports the gap as cleanliness. staleref got the same treatment earlier the same day — it now prints a census of the extensions it walked past, after reporting 1 finding over "237 doc file(s)" where --ext hcl found 72. Three tools, one defect class, and in every case the number was right and the missing thing was the sentence saying what it covered.

v0.133.0

Compare Source

What's Changed

  • fuzz: a nightly workflow that fuzzes every target by @​tannevaled in #​341
  • staleref: say "N of M file(s) read" and name what was walked past, because the warning in --help is read before the zero arrives by @​tannevaled in #​342

Full Changelog: go-fleettools/fleettools@v0.132.0...v0.133.0

v0.132.0

Compare Source

What's Changed

  • vmkey: grant before removing inheritance, check, then lock; recover a lock-out by @​tannevaled in #​340

Full Changelog: go-fleettools/fleettools@v0.131.0...v0.132.0

v0.131.0

Compare Source

What's Changed

  • staleref: the context window cut mid-rune, so grep refused the whole report and 15 findings read as a clean tree by @​tannevaled in #​337
  • staleref: --max-unsure, so a rename's prose tail can be a ratchet instead of a reason the gate stays off by @​tannevaled in #​338
  • Add cmd/vmkey: install one SSH key for a non-admin user on a loopback VM by @​tannevaled in #​339

Full Changelog: go-fleettools/fleettools@v0.130.0...v0.131.0

v0.130.0

Compare Source

What's Changed

  • gotest: refuse a benchmark on a busy machine, and stop failing a bench run for its empty test selection by @​tannevaled in #​336

Full Changelog: go-fleettools/fleettools@v0.129.0...v0.130.0

v0.129.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.128.0...v0.129.0

v0.128.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.127.1...v0.128.0

v0.127.1

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.127.0...v0.127.1

v0.127.0

Compare Source

What's Changed

  • recur: a replacement says what it replaces, and a landed gate is not downgraded in silence by @​tannevaled in #​316

Full Changelog: go-fleettools/fleettools@v0.126.0...v0.127.0

v0.126.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.125.0...v0.126.0

v0.125.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.124.1...v0.125.0

v0.124.1

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.124.0...v0.124.1

v0.124.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.123.0...v0.124.0

v0.123.0

Compare Source

modtidy names its two non-verdicts instead of guessing them (#​301, closing
#​294 and #​300). Both were measured on 2026-11-15, and both were places where
the gate answered where it could not know.

A module with no Go source is skipped, with the reason named. go mod tidy can only REMOVE requirements there, so its verdict carries no
information — and the remedy it prescribed destroyed the repository: on a clean
go-fft/docs clone the hook returned deny with text telling the next session
to run go mod tidy and commit go.mod and go.sum, which deletes the Hugo
theme from both. The signal is "no .go file of its own", decided before go
runs, so it needs neither toolchain nor network. A Hugo configuration is
reported, never what decides: that site has no [module] block, so a rule
keyed on one would have missed its own occurrence. A nested module's sources
never answer for its parent, and a file behind a build constraint still counts,
so a //go:build tools file keeps a module judged.

A go directive above the installed toolchain is retried once with the
toolchain the directive names.
GOTOOLCHAIN=local on a host whose Go is
older cannot build such a module at all, and in the hook UNREAD means allow —
so the gate had gone silently off for every repository raised to go 1.27.4,
this one included: modtidy could not read go-fleettools/fleettools. The
retry reproduces CI rather than loosening the check, since CI's runner has the
version the directive requires. Not GOTOOLCHAIN=auto, which would leave the
version unstated. The report names the toolchain that answered.

A broken go.mod is still UNREAD, never skipped: skipping is a clean answer,
and "no .go file" does not read the file that is wrong. The repository's own
corpus caught that during review of the change.

Breaking: nothing for callers. The report gains a fourth class and a fourth
figure in its summary line, so anything parsing that line sees one more count.

v0.122.0

Compare Source

What's Changed

  • landingmigrate: resolve buttons that read hugo.toml; migrate --follow-logo by @​tannevaled in #​299

Full Changelog: go-fleettools/fleettools@v0.121.0...v0.122.0

v0.121.0

Compare Source

What's Changed

  • landingmigrate repeats: hide a card's architectures sentence under the goarch condition by @​tannevaled in #​297

Full Changelog: go-fleettools/fleettools@v0.120.0...v0.121.0

v0.120.0

Compare Source

What's Changed

  • landingmigrate repeats: hide strip-subject feature cards and a bare Pure Go footer by @​tannevaled in #​296

Full Changelog: go-fleettools/fleettools@v0.119.0...v0.120.0

v0.119.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.118.0...v0.119.0

v0.118.0

Compare Source

What's Changed

  • landingmigrate upgrade: bring a landing already on the kit to the current recipe by @​tannevaled in #​293

Full Changelog: go-fleettools/fleettools@v0.117.0...v0.118.0

v0.117.0

Compare Source

What's Changed

  • landingmigrate: hide the tagline's repeat of the strip; refuse a button built from an expression by @​tannevaled in #​292

Full Changelog: go-fleettools/fleettools@v0.116.1...v0.117.0

v0.116.1

Compare Source

What's Changed

  • testwhy: read the Actions log prefix, refuse an unread log; replystamp: visible-block wording by @​tannevaled in #​291

Full Changelog: go-fleettools/fleettools@v0.116.0...v0.116.1

v0.116.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.115.0...v0.116.0

v0.115.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.114.0...v0.115.0

v0.114.0

Compare Source

What's Changed

  • landingmigrate: the external-stylesheet template; the hero row from the kit by @​tannevaled in #​285

Full Changelog: go-fleettools/fleettools@v0.113.0...v0.114.0

v0.113.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.112.0...v0.113.0

v0.112.0

Compare Source

What's Changed

  • replystamp --pretool: judge the first text's stamp; re-read before a no-text deny by @​tannevaled in #​278

Full Changelog: go-fleettools/fleettools@v0.111.0...v0.112.0

v0.111.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.110.0...v0.111.0

v0.110.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.109.0...v0.110.0

v0.109.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.108.0...v0.109.0

v0.108.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.107.0...v0.108.0

v0.107.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.106.0...v0.107.0

v0.106.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.105.0...v0.106.0

v0.105.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.104.0...v0.105.0

v0.104.0

Compare Source

runson — which runner images the fleet's workflows ask for

A new command, and the last fleet tool that was living outside a repository (fleettools#201 item 2).

runson                           # the distribution, over every checkout
runson --value ubuntu-26.04-arm  # WHICH repositories ask for it
runson --fail-on ubuntu-latest   # exit 1 while anything still does

Zero API calls: asking GitHub would be ~20 requests across ~1400 repositories, several times the hourly budget the Renovate runners share. It reads the checkouts already on disk, counting repositories rather than files — one repository with nine lanes is not nine exposures.

First pass: 1317 checkouts, 1247 with workflows, 3599 findings.

runs-on repos
ubuntu-latest 1226
${{ matrix.os }} 293
macos-latest 59
windows-latest 41
ubuntu-24.04-arm 40
ubuntu-26.04-arm 4

Written for the upstream migration of ubuntu-latest (x64) to Ubuntu 26.04 between 2026-10-19 and 2026-11-19: inside that window a red CI can be the image moving while the repository did not.

The staleness is measured, not disclaimed

Reading a disk costs you currency of evidence, and this says how much rather than warning you vaguely:

⚠ 842 of the 1247 CHECKOUTS read are BEHIND their remote (furthest: 188 commits).
  A workflow added upstream since is invisible here, so this UNDERSTATES exposure.
⚠ 405 of the 1247 CHECKOUTS read have not FETCHED for over 1h0m0s, so a distance
  of 0 means nobody asked, not that they are current.

842 + 405 = 1247: not one checkout is confirmed current. The direction is stated too — a checkout predating a newly added workflow makes the count a floor, and an absence read off a stale disk looks exactly like an absence that is real.

Refusals
  • An empty population exits 2, not 0 with an empty table: pointed at a root with the wrong layout, "nothing asks for ubuntu-latest" and "nothing was read" are different answers.
  • ${{ matrix.os }} and [self-hosted, linux] are reported verbatim rather than resolved, because a wrong resolution is worse than an honest indirection.

Full notes in #​239.

v0.103.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.102.0...v0.103.0

v0.102.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.101.0...v0.102.0

v0.101.0

Compare Source

What's Changed

  • secondorigin: verify a second origin against its declaration; init its Pages repository by @​tannevaled in #​236

Full Changelog: go-fleettools/fleettools@v0.100.0...v0.101.0

v0.100.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.99.0...v0.100.0

v0.99.0

Compare Source

What's Changed

  • staleref: a fork keeps citing what it forked from, so a grep cannot find the drift by @​tannevaled in #​227
  • staleref: --keep, because 53 of 60 stale addresses were the LIVE registry by @​tannevaled in #​228
  • priorart: a careful subject no longer loses the tracker, and a hit no longer masks an unread surface by @​tannevaled in #​230

Full Changelog: go-fleettools/fleettools@v0.98.0...v0.99.0

v0.98.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.97.0...v0.98.0

v0.97.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.96.0...v0.97.0

v0.96.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.95.0...v0.96.0

v0.95.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.94.0...v0.95.0

v0.94.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.93.0...v0.94.0

v0.93.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.92.0...v0.93.0

v0.92.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.91.0...v0.92.0

v0.91.0

Compare Source

What's Changed

  • ghissue --edit and ghrel: edit issues, edit/upload/delete existing releases by @​tannevaled in #​214

Full Changelog: go-fleettools/fleettools@v0.90.0...v0.91.0

v0.90.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.89.0...v0.90.0

v0.89.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.88.0...v0.89.0

v0.88.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.87.0...v0.88.0

v0.87.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.86.0...v0.87.0

v0.86.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.85.0...v0.86.0

v0.85.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.84.1...v0.85.0

v0.84.1

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.84.0...v0.84.1

v0.84.0

Compare Source

What's Changed

Full Changelog: go-fleettools/fleettools@v0.83.0...v0.84.0

v0.83.0

Compare Source

--verify-origin: the report described one disk

pinscan walks go.mod files in the working tree. About 25 sessions hold
clones of very different ages on this machine, so a six-day-old clone writes
the same bytes as a stale pin — and nothing in the output said which tree was
read.

Re-reading each declaring repository's go.mod from GitHub:

verified against origin: 11 still declare one, 53 already fixed, 5 unreadable

53 of 64 were already fixed upstream. The eleven real ones are
go-pdfkit/pdfkit, go-ruby-fsctl/fsctl, `go-slid

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@tannevaled tannevaled changed the title chore(deps): update module github.com/go-fleettools/fleettools to v0.73.0 chore(deps): update module github.com/go-fleettools/fleettools to v0.79.0 Nov 6, 2026
@tannevaled tannevaled changed the title chore(deps): update module github.com/go-fleettools/fleettools to v0.79.0 chore(deps): update module github.com/go-fleettools/fleettools to v0.80.0 Nov 7, 2026
@tannevaled tannevaled changed the title chore(deps): update module github.com/go-fleettools/fleettools to v0.80.0 chore(deps): update module github.com/go-fleettools/fleettools to v0.84.1 Nov 8, 2026
@tannevaled tannevaled changed the title chore(deps): update module github.com/go-fleettools/fleettools to v0.84.1 chore(deps): update module github.com/go-fleettools/fleettools to v0.91.0 Nov 9, 2026
@tannevaled tannevaled changed the title chore(deps): update module github.com/go-fleettools/fleettools to v0.91.0 chore(deps): update module github.com/go-fleettools/fleettools to v0.98.0 Nov 10, 2026
@tannevaled tannevaled changed the title chore(deps): update module github.com/go-fleettools/fleettools to v0.98.0 chore(deps): update module github.com/go-fleettools/fleettools to v0.104.0 Nov 11, 2026
@tannevaled tannevaled changed the title chore(deps): update module github.com/go-fleettools/fleettools to v0.104.0 chore(deps): update module github.com/go-fleettools/fleettools to v0.105.0 Nov 12, 2026
@tannevaled tannevaled changed the title chore(deps): update module github.com/go-fleettools/fleettools to v0.105.0 chore(deps): update module github.com/go-fleettools/fleettools to v0.108.0 Nov 13, 2026
@tannevaled tannevaled changed the title chore(deps): update module github.com/go-fleettools/fleettools to v0.108.0 fix(deps): update dependencies Nov 14, 2026
@tannevaled
tannevaled force-pushed the renovate/deps branch 5 times, most recently from 10422ba to d9ab46e Compare November 19, 2026 03:55
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