mirror of
https://github.com/lukaszraczylo/traefik-llmgateway.git
synced 2026-10-12 04:54:45 +00:00
lukaszraczylo
45b650410d
A go test run over ./... stops at nested modules, so CI never ran tools/pricing-sync or the Yaegi interpreter check. A new job runs both with Go 1.25.x. The go.sum of tools/yaegi-check now holds its test dependencies, and its go.mod lists the prometheus modules as direct dependencies. The .gitattributes comment now says that the export-ignore rules for tools/, webui/, examples/ and testdata/ do take effect. Claude-Session: https://claude.ai/code/session_01V5jYJNxpDFdJkyyExpADrv
83 lines
4.6 KiB
Plaintext
83 lines
4.6 KiB
Plaintext
# export-ignore controls what `git archive` leaves out of the tree it
|
|
# packs. GoReleaser's `source:` block runs `git archive` under the hood
|
|
# (.goreleaser.yaml), so these entries are the actual filter for the
|
|
# release source tarball — not the archive block's own file globs, which
|
|
# have no negation syntax and cannot exclude anything.
|
|
# vendor/ is deliberately NOT export-ignored, and must stay that way.
|
|
#
|
|
# It WAS export-ignored until 2026-08-23, on the reasoning that every
|
|
# dependency was test-only (github.com/stretchr/testify and its
|
|
# go.yaml.in/yaml/v3 indirect), imported solely by *_test.go files that
|
|
# are themselves export-ignored below — so the tarball never contained
|
|
# code needing vendor/ to build. That comment carried an explicit warning
|
|
# to remove the line the moment production code imported a third-party
|
|
# package.
|
|
#
|
|
# That happened, and the warning was missed: llmgateway.go took on
|
|
# github.com/lukaszraczylo/oss-telemetry as a RUNTIME dependency. The
|
|
# release tarball then shipped a go.mod requiring a module whose source
|
|
# had been stripped, and the Traefik Plugin Catalog analyzer (piceus)
|
|
# rejected v1.0.43 with:
|
|
#
|
|
# import "github.com/lukaszraczylo/oss-telemetry" error:
|
|
# unable to find source related to: "github.com/lukaszraczylo/oss-telemetry"
|
|
#
|
|
# piceus fetches the source ARCHIVE at the released tag and interprets it
|
|
# with Yaegi. It never runs `go mod download`, so every non-stdlib import
|
|
# in production code must be present in the archive's own vendor/ tree.
|
|
# Shipping vendor/ also costs the test-only deps a few hundred KB in the
|
|
# tarball, which is the correct trade against being unimportable.
|
|
integration/ export-ignore
|
|
tools/ export-ignore
|
|
docs/ export-ignore
|
|
examples/ export-ignore
|
|
testdata/ export-ignore
|
|
# cmd/gateway/testdata/ holds a real captured production config used as the
|
|
# config-loader test fixture. It carries no key material (every provider key
|
|
# in it is a `file:` reference resolved from a mounted volume), but it does
|
|
# carry in-cluster hostnames and addresses that have no business in a public
|
|
# catalog tarball.
|
|
#
|
|
# Written as `/**`, not as a trailing-slash directory pattern like the
|
|
# lines above, so `git check-attr export-ignore --` can confirm THIS one
|
|
# line is live for a specific file path (P5, review round 4: the
|
|
# trailing-slash form below is NOT broken — see the next paragraph — this
|
|
# is only about what check-attr itself can verify). `git check-attr`
|
|
# evaluates a pattern as if for a FILE, and a pattern ending in "/"
|
|
# matches only a directory, so it always reports "unspecified" for a
|
|
# trailing-slash pattern regardless of whether git archive actually
|
|
# honours it; `/**` sidesteps that check-attr quirk. Verified with `git
|
|
# check-attr export-ignore --`: this line reports "set", while a
|
|
# `cmd/gateway/testdata/` form reported "unspecified" even though (next
|
|
# paragraph) that form still works for git archive.
|
|
#
|
|
# The same check reports "unspecified" for tools/, webui/, examples/ and the
|
|
# repo-root testdata/ above — but that is a `git check-attr` quirk, NOT
|
|
# evidence those lines are no-ops. check-attr evaluates the attribute as if
|
|
# for a FILE, and a pattern ending in "/" only ever matches a directory, so
|
|
# it reports "unspecified" for any per-file path you hand it, whether or
|
|
# not the pattern actually governs that path. `git archive` walks the tree
|
|
# and applies export-ignore to each directory ENTRY it visits, which a
|
|
# trailing-slash pattern matches directly — verified: `git archive
|
|
# --worktree-attributes HEAD | tar -t | grep -c '^tools/'` (and the same for
|
|
# webui/, examples/, testdata/, integration/, .github/) all print 0, i.e.
|
|
# every file under each of those directories is excluded from the release
|
|
# tarball today. These lines are live, not no-ops — do not "fix" them to
|
|
# `/**` (harmless, but unnecessary) or delete them as dead weight (deleting
|
|
# them would send ~250 test and tooling files into the catalog tarball).
|
|
# The *_test.go and .gitattributes lines below reach the same outcome
|
|
# through an ordinary no-slash pattern, which check-attr reports correctly
|
|
# for both a file and a directory path — hence no similar-looking discrepancy
|
|
# there.
|
|
cmd/gateway/testdata/** export-ignore
|
|
.superpowers/ export-ignore
|
|
.github/ export-ignore
|
|
*_test.go export-ignore
|
|
.gitattributes export-ignore
|
|
# webui/ is the Vue admin panel's SOURCE (Vite/npm project) — CI and a
|
|
# release build never need node: admin_assets_gen.go (repo root, `make
|
|
# admin-ui`'s committed output) is the only artifact the plugin build
|
|
# actually depends on, exactly like vendor/ above is safe to drop because
|
|
# nothing at the repo root imports it directly.
|
|
webui/ export-ignore
|