Skip to content

History

Revisions

  • wiki: reconcile with the 1.13.0 codebase + open up the components gap Verified against the nuget.org package list and the tamp-build org. Module-Catalog: - Tamp.Core "Current: 1.11.1" -> 1.13.0. - Note the 1.12.0 split: the six security wrappers now ship from their own satellite repos on a version line that has diverged from Tamp.Core's. Only Tamp.Sarif / Tamp.Sbom / Tamp.Security.Pipeline remain in the core repo. - Add Tamp.Telemetry and Tamp.Ingest.V1 to the telemetry section, which previously listed only the tamp-beacon server and no NuGet packages. - Add tamp-findings (attestation / federal-readiness evidence dashboard). - New Accessibility section for Tamp.AxeCore. Home: add Tamp.Kubectl, Tamp.AxeCore, Tamp.Telemetry, Tamp.Ingest.V1. Migrating-From-NUKE: the components section said Tamp.Components was "a Tier 3 plan", which reads as scheduled work. It isn't — it is not designed, not built and not scheduled. Say so plainly, tell migrators what to write by hand in the meantime, and invite an ADR from anyone with a real components-shaped build, since they are better placed to design it than the maintainers are.

    @BrewingCoder BrewingCoder committed Jul 13, 2026
    1f33ea1
  • wiki: refresh Module-Catalog + Analyzers + Home + sidebar + FAQ + Getting-Started 10 days of ecosystem growth had drifted the wiki out of sync. ## Module-Catalog - Bump satellite count framing from 40+ to 50+ (current actual via nuget profile listing) - Bump Tamp.Core version refs from 1.6.0 to 1.11.1 throughout - New section: Classic Windows deploy chain (Wave 4) — SqlPackage, SqlCmd, MSBuildClassic, MsDeploy - Expanded supply-chain security section: split into Contract packages (Sarif, Sbom), SBOM producers (CycloneDx.V6, Syft), scanners (TruffleHog/CodeQL/OpenGrep/OsvScanner/Trivy/Grype/ SonarScanner/Eslint), triage sinks (DependencyTrack.V1, DefectDojo.V2), and the one-import Security.Pipeline meta - New section: Notifications — Tamp.Telegram (with Slack/Discord siblings flagged as planned) - New section: Telemetry/observability backend — tamp-beacon self-host server - New section: Editor integration — Tamp for VS Code (vsix sideload from GitHub Releases; Marketplace deferred) - Add Tamp.Eslint.V9 to JS/TS toolchain section - Add Tamp.GitHubAttest to source-control section - Add Tamp.AdjacentContainer.Local to containers section - Replace stale Tamp.OpenGrep.V1 / Tamp.Syft.V1 references with the renamed Tamp.OpenGrep / Tamp.Syft (per the 1.11.1 reconcile); added an explicit 'Naming reconcile' subsection explaining the rename and that old packages remain on nuget at 1.11.0 - Add Tamp.Eslint.V9 + Tamp.MSBuildClassic to the naming convention examples - New Common stack: 'Hybrid / modernized .NET on-prem deploy' using MSBuildClassic + SqlPackage + SqlCmd + MsDeploy ## Tamp-Analyzers - Bump header range from TAMP001-TAMP004 to TAMP001-TAMP006 - New TAMP005 section (FromPath field shadowing; <Tool>Bin convention) - New TAMP006 section (Target property shadowing) - New section: Reflection-bound field warning suppressor (CS0649 false-positive suppression for [Parameter] / [Secret] / [Solution] / etc. fields) ## Home - 40+ → 50+ satellite count - Analyzer range TAMP001-TAMP004 → TAMP001-TAMP006 - Add Tamp.Eslint.V9 to JS toolchain inline list - Add Classic Windows deploy chain (Wave 4) bullet - Expand Supply-chain security bullet to cover the full Wave 1+2+3 chain (foundation contracts, producers, scanners, sinks, meta) - New Notifications bullet (Tamp.Telegram) - New Editor integration section pointing at tamp-build/tamp-vscode + flagging the planned Fleet sibling - Add ADR-0018 diagnostics emission contract bullet to Execution and observability section - Add Tamp.Sarif, Tamp.Sbom, Tamp.Templates.AspNet to Foundation - Add Tamp.GitHubAttest to source-control ## _Sidebar - 'Module Catalog (canonical list, 50+ satellites)' - TAMP001-TAMP004 → TAMP001-TAMP006 - New 'Editor integration' nav section pointing at tamp-vscode ## FAQ - Pre-1.0 framing was stale (Tamp.Core 1.x has been GA since 2026-05-10) → updated to reflect prod-ready posture with the dogfood-Release-pipeline supporting evidence - '40+ satellites' → '50+' - Tamp.Core version refs in min-version examples: 1.6.0 → 1.11.1 ## Getting-Started - Resolved contradiction between 'Templates (0.2.0+)' section (listing minimal/library/monorepo) and 'Template selection (preview)' section (claiming only minimal ships). All three templates DO ship today per Tamp.Cli source — removed the stale 'preview' caveat and replaced with a 'Template availability' section clarifying embedded vs NuGet-distributed template resolution.

    @BrewingCoder BrewingCoder committed May 25, 2026
    22ae6dc
  • docs(TAM-161): mention tamp init --settings-style=init + per-tool dual-style pointer - Build-Script-Authoring §"Two authoring styles" now points at the new `tamp init --settings-style=init` scaffold flag. - Each per-tool page (NetCli, Docker, Yarn, Vite, Playwright, Turbo, TruffleHog, CodeQL, GraphQLCodegen, Analyzers) gets a uniform "Settings authoring style" section near the bottom pointing back at the side-by-side comparison in Build-Script-Authoring. Fluent stays canonical in every example body — the new section just flags that object-init exists and where to read about it.

    @BrewingCoder BrewingCoder committed May 15, 2026
    f66a72c
  • Wiki sweep — TAM-207 / TAM-119 / TAM-213 surfaces Build-Script-Authoring: - Document --skip <target> / --skip-deps / --format=text|json / --reporter=text|json flags (Tamp.Core 1.9.0) - Skipping targets section with adopter use cases + typo-protection note Getting-Started: - New "Templates (0.2.0+)" section showing the three embedded templates (minimal / library / monorepo) with usage - Update file-list table to include tamp.sh + tamp.cmd shims (5 files written by tamp init) - --template / --force flag reference Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @BrewingCoder BrewingCoder committed May 13, 2026
    becf920
  • Add Paths-And-Filesystem reference page + sidebar entry + NUKE-migration crosslink Canonical reference for the AbsolutePath FS surface (existing + new in Tamp.Core 1.8.0). DasBook canary feedback: adopters scanning READMEs without a dedicated wiki page never built a complete mental model of what AbsolutePath could do, leading to redundant System.IO drops. Covers: construction + components + existence + creation/deletion + read/write + copy/move + hashing + globbing + OS temp-path factories + TampBuild.Scratch lifecycle. Closes the loop on the "Tamp.FileSystem satellite" design question (TAM-202) — answered as "no satellite, native on AbsolutePath". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @BrewingCoder BrewingCoder committed May 13, 2026
    206c731
  • docs(wiki): add Tamp.AdjacentContainer.Provisioning + Tamp.YouTrack to Module-Catalog Both shipping at 0.1.0 in the current release wave: - Tamp.AdjacentContainer.Provisioning (TAM-164) — CI-side companion to Tamp.AdjacentContainer. Builds deterministic docker-compose YAML for sidecar resources and emits the env-var contract that the fixture-side reads. Pairs with Tamp.Docker.V27.Docker.Compose.Up/Down for lifecycle. - Tamp.YouTrack (TAM-180) — typed YouTrack REST client. Issues create / update / search / set-state. Bearer auth via Secret-typed permanent token. Built on Tamp.Http. Tamp.AdjacentContainer.Provisioning sits in the Containers + build row group next to its fixture-side sibling. Tamp.YouTrack lands in the Azure + ADO ops row group alongside the other typed REST clients (Tamp.AdoRest.V7, Tamp.Kudu, etc).

    @BrewingCoder BrewingCoder committed May 13, 2026
    df2170d
  • docs(wiki): clarify satellite-to-Tamp.Core version semantics Add a "How satellites depend on Tamp.Core" section to Module-Catalog.md explaining: - NuGet PackageReference Version="1.6.0" is min-version (>= 1.6.0), not a pin — the satellite-sweep-per-Core-bump pattern we were doing was unnecessary except when needing new Core API or IVT (the latter retired in 1.6.0 via TAMP004). - Decision table: when does a satellite actually need to bump its Core minimum? (Patch/minor: no. Wants new API: yes. New analyzer trip: yes. Major: yes.) - Why this matters for the recent onboarding wave's velocity. - NuGet range-syntax reference table — npm-style ranges supported, but first-party satellites stay on bare 1.6.0 form since tighter pinning is an adopter choice. Add corresponding FAQ entry: "When Tamp.Core ships a new minor, do all 40+ satellites need to re-publish?" with the short answer and a link to the Module Catalog section. Both are documentation of existing semantics — no satellite changes needed.

    @BrewingCoder BrewingCoder committed May 13, 2026
    18adddb
  • Refresh wiki for 1.6.0 + 40+ satellite reality - Module-Catalog.md: rewrote the package table grouped by category. Added 30+ missing satellites (Cargo, Tauri, Msix, MicrosoftStoreCli, Sccache, Syft, Grype, Kudu, AzureCli, EFCore, GitVersion, ReportGenerator, GitHubCli, Helm, Bicep, AzureAppService, PostgresFlex, AdoGit, AdoRest, AdoServiceConnection, Npm, AzureFunctionsCoreTools, AzureStaticWebApps, ServiceBus, Coverlet, Testcontainers, AdjacentContainer, Http, etc.). Added "Common stacks" worked-examples section linking the new families (Microsoft Store ship chain, Azure-deployed .NET service, Helm-deployed cluster app, compliance-aware ship). Surface notes about 1.2.0 (object-init) and 1.6.0 (TAMP004) at the top. - Home.md: rewrote the Modules section to surface all the new families; added an Analyzers section linking the new Tamp-Analyzers page. - _Sidebar.md: grouped modules by category (.NET, containers, JS, supply- chain security) for navigability; added Analyzers link. - Tamp-Analyzers.md (new): full reference for TAMP001 / TAMP002 / TAMP003 / TAMP004 with bug-class examples, fix patterns, and approved-context rules. Explains why 1.6.0 retired the per-satellite IVT gate in favor of TAMP004. - Parameter-And-Secret-Injection.md: removed "Status: v0" note (we're at 1.6); updated the Secret section to reflect public Reveal() + TAMP004 gating + pre-1.6.0 history. Doc refresh out of the DasBook + Strata + HoldFast onboarding wave that shipped 6 satellites + Tamp.Core 1.6.0 in one evening. The wiki was ~9 months stale on satellite count.

    @BrewingCoder BrewingCoder committed May 13, 2026
    e24e26c
  • docs: add non-.NET stack story + BuildProject attribute to Getting Started - New "What if I'm not building a .NET project?" section. Tamp build scripts are .NET (framework runtime) but what they build can be anything — React, Python, Rust, Helm, polyrepo. - Document [BuildProject(Name=..., Area=...)] as the language-agnostic primary path for polyrepo project identification (1.4.0+, ADR 0018). - Cross-link from Where-next. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @BrewingCoder BrewingCoder committed May 12, 2026
    3e91141
  • docs: 1.3.0 surface — Pitfalls page, Common idioms, Docker.Push answers - New Pitfalls page covering CleanArtifacts blast radius (HoldFast friction #12 headliner), yarn berry post-disaster recovery, and BuildKit migration warnings (SecretsUsedInArgOrEnv informational lint when moving from legacy docker build → buildx). - Build-Script-Authoring gains a Common idioms section: image-tag from SemVer + commit sha, fan-out target with the 1.3.0 params Target[] DependsOn overload, post-deploy smoke probe with HttpProbe.WaitForHealthy. - Tamp-Docker extended with Docker.Push multi-tag (Tag-then-push and buildx-time multi-tag-push), insecure-registry (daemon config, not a wrapper flag), and Secret credential idioms (Docker.Login with Password=Secret → --password-stdin, or ~/.docker/config.json fall- back for ARC-runner contexts). New buildx-migration-warnings call- out links back to Pitfalls. - Sidebar links the new Pitfalls page under Reference. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @BrewingCoder BrewingCoder committed May 12, 2026
    d1e58c9
  • docs: refresh for 1.2.0 surface — Internal/Default/CleanArtifacts/object-init - Build-Script-Authoring: anatomy uses 1.1.0+ surface (Internal/Default, CleanArtifacts, no .TopLevel(), object-init authoring style); lifecycle table marks TopLevel() obsolete; Default/Ci shortcuts updated. - Module-Catalog: module-shape example shows both fluent and object-init. - Getting-Started: scaffolded Build.cs uses .Default() and drops the obsolete TopLevel() marker. - Glossary: Internal and Default entries replace TopLevel; Wrapper entry notes the 1.2.0 dual-style overloads. - Migrating-From-NUKE: Unlisted → Internal mapping (renamed in 1.1.0+); migration recipe step 7 updated; .TopLevel() noted as obsolete on upgrade. - Tamp-NetCli: Push target example stripped of .TopLevel(). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @BrewingCoder BrewingCoder committed May 11, 2026
    b4df43d
  • docs: Wave 5 — HoldFast trial doc sweep (TAM-107, 110, 114, 117) - Parameter-And-Secret-Injection: add canonical [FromPath] and [FromNodeModules] sections (Tamp.Core 1.0.8+). Note that [NuGetPackage(..., UseSystemPath = true)] is legacy — preferred path is now the dedicated attributes which handle Windows extension probing (.cmd / .exe / .bat / .ps1) correctly. Updated resolution- timing list to mention the new attrs. - Module-Catalog: bump Tamp.Docker.V27 row to flag the 0.3.0 breaking change (Docker.Build → BuildKit; Docker.LegacyBuild for the old builder). Note Tamp.NetCli 1.0.9+ adds DotNet.Clean and solution-mode TRX auto-disambiguation. - Tamp-Turbo: rewrite quick example to use [FromNodeModules("turbo")] (with [FromPath("turbo")] mentioned as the global-install alternative). Add an explicit "multi-value flags are collection- shaped — Add* not Set*" callout matching TAM-114. - Tamp-Docker: full rewrite of the Docker.Build section. Documents BuildKit-by-default semantics, the buildx-shaped settings surface, and the LegacyBuild fallback. Migration guide from 0.2.0 included. Covers HoldFast trial frictions: TAM-107 — Log symbol misdirection (the wiki was already correct; this pass closes the loop by making sure the canonical examples don't drift back) TAM-110 — DotNetTestSettings AddLogger vs SetLogger (docs were already AddLogger-correct; closed by reinforcing the Add* vs Set* convention in the Turbo callout) TAM-114 — TurboRunSettings AddTasks/AddFilter clarification TAM-117 — Docker.Build BuildKit default + migration

    @BrewingCoder BrewingCoder committed May 11, 2026
    a7f4898
  • Add 7 HoldFast wrapper pages; refresh Module-Catalog + Home + Sidebar Per-wrapper pages added: Tamp-Yarn, Tamp-Turbo, Tamp-Vite, Tamp-GraphQLCodegen, Tamp-Playwright, Tamp-TruffleHog, Tamp-CodeQL. Each follows the Tamp-Docker.md / Tamp-NetCli.md house style: intro -> verbs -> CI behavior gotchas -> quick example -> See also. Module-Catalog table now lists all 14 first-party packages, the DotNetCoverage and SonarScanner / EFCore / GitVersion / ReportGenerator / GitHubCli rows that were missing, and a note about the reserved Tamp.* NuGet prefix. Home modules section grouped by domain (JS toolchain / testing / security scanning) for easier scanning at the Tamp ecosystem's new size. Sidebar adds nav links for all 7 new wrapper pages. Naming-convention table updated: dropped "Tamp.Yarn (planned)" since it's now shipping pinned as V4 (Berry 4 broke from classic Yarn); added Tamp.Vite.V5 as another live pinned example.

    @BrewingCoder BrewingCoder committed May 11, 2026
    d02f8c0
  • Document DotNet.NuGetPush in Tamp-NetCli reference

    @BrewingCoder BrewingCoder committed May 10, 2026
    ffc402c
  • Wiki content: build authoring, modules, primitives, CI hosts, migration, FAQ, glossary

    @BrewingCoder BrewingCoder committed May 10, 2026
    927631e
  • Initial Home, Getting Started, navigation chrome

    @BrewingCoder BrewingCoder committed May 10, 2026
    0af4d69
  • Initial Home page

    @BrewingCoder BrewingCoder committed May 10, 2026
    41efbb2