Skip to content

fix(deps): landingkit v0.7.0, the strip as text - #54

Merged
tannevaled merged 2 commits into
mainfrom
fix/landingkit-v0.7.0
Oct 24, 2026
Merged

tannevaled merged 2 commits into
mainfrom
fix/landingkit-v0.7.0

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

Bumps go-fleettools/landingkit to v0.7.0 (go-fleettools/landingkit#15).

Up to v0.6.0, the strip under the top bar (LICENSE=BSD-3-Clause, CGO_ENABLED=0, and any data chip) was CSS generated content. It looked right in a screenshot but was absent from the page's text, so pagetext found neither value. v0.7.0 renders the strip as text. landingmigrate strip checked this on the built page:

strip text: LICENSE=BSD-3-Clause | CGO_ENABLED=0

🤖 Generated with Claude Code

tannevaled and others added 2 commits October 24, 2026 07:32
Up to v0.6.0 the strip under the top bar (LICENSE=BSD-3-Clause,
CGO_ENABLED=0, any data chip) was CSS generated content: right in a
screenshot, absent from the page's text, so it could not be selected,
found, indexed or reliably read. v0.7.0 renders it as text. Checked on the
built page with landingmigrate strip.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
landingkit v0.7.0 declares go 1.27.3 (GO-2026-6809 is fixed there); the workflows pinned 1.27.2 with GOTOOLCHAIN=local and could not load the module.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tannevaled
tannevaled merged commit a7c571a into main Oct 24, 2026
7 checks passed
@tannevaled
tannevaled deleted the fix/landingkit-v0.7.0 branch October 24, 2026 05:42
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