📦 deps: refresh dev-tooling + sigstore-go for v1.4 soak#103
Merged
Conversation
Upstream agent renamed CodesWhat/lookout → CodesWhat/portwing, so the bundled preset follows. Pure rename, no rule changes. - 🔄 refactor(configs): lookout.yaml → portwing.yaml, lookout-with-exec.yaml → portwing-with-exec.yaml - 🔄 refactor(examples): examples/compose/lookout/ → examples/compose/portwing/ - 📝 docs(presets): retitle Lookout sections, update agent URL, fix cross-references - 📝 docs(readme,changelog): update preset list, compose-example list, and v1.4 changelog entry
Replace the logo everywhere it ships and regenerate every derived icon from the new 1023x1023 source. - 🎨 style(logo): new sockguard-logo.png at repo root, website/public, docs/public (all three kept byte-identical as before) - 🎨 style(favicons): regenerate favicon.ico (16/32/48), favicon-96x96.png, apple-touch-icon.png, favicon.svg — transparency preserved - 🎨 style(pwa): regenerate maskable web-app-manifest 192/512 (logo padded to safe zone, flattened on white) to match prior output - 🔧 config(layout): bump icon cache-buster ?v=20260408 → ?v=20260615 so returning visitors refetch
Replace the old ASCII banner with the sockguard dog, and render it in full 24-bit colour on capable terminals with a clean monochrome fallback. - 🎨 style(banner): swap the banner art for the block-glyph dog (▓▒░█), 53 cols - ✨ feat(banner): embed a 50-col half-block truecolor render (dog_color.ans), shown when the terminal advertises COLORTERM=truecolor/24bit - 🐛 fix(banner): count runes not bytes in artMaxWidth — the block glyphs are 3 bytes each, so len() overcounted ~3x and broke centering - 🔄 refactor(banner): centerArt takes an explicit width arg, so it centers both the rune-measured monochrome art and the ANSI-laden colour art - 🧪 test(banner): measure width locally in the test helper instead of mutating package state
- 📦 deps(go): bump sigstore/sigstore-go v1.2.0 → v1.2.1 (image-trust path; no behavior change) - 📦 deps(npm): Biome 2.4.16 → 2.5.0 - 📦 deps(npm): Tailwind 4.3.0 → 4.3.1; pin docs in lockstep with website - 📦 deps(npm): fumadocs 16.10.0 → 16.10.3, lucide-react 1.17 → 1.18, @radix-ui/react-slot 1.2 → 1.3 - 🔒 security(deps): regen lockfile from scratch so the postcss override resolves (npm audit: 0 vulnerabilities)
scttbnsn
requested review from
ALARGECOMPANY and
biggest-littlest
as code owners
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Small dependency-refresh batch on
dev/v1.4.Go
sigstore/sigstore-gov1.2.0 → v1.2.1 (image-trust path; patch, no behavior change)go mod tidy'd;govulncheckcleannpm (dev/docs tooling)
^4.3.0; pinned docs to 4.3.1 so both build the same Tailwind@radix-ui/react-slot1.2 → 1.3Lockfile / postcss
npm updateleft next's nested postcss flagged (the override doesn't re-resolve on update — the known full-reinstall trap). Regeneratedpackage-lock.jsonfrom scratch in a clean env so the existingpostcss: ^8.5.15override is authoritative —npm auditreports 0 vulnerabilities.Checks
Full pre-push chain green: go-lint, go-test, govulncheck, go-fuzz, lockfile-dedupe, knip, biome, ts-test, build, zizmor, clean-tree.