- build-ssm-plugin.{sh,ps1}: skip the vendored SDK's Java codegen/ and
test snapshot/ trees when extracting (codegen paths reach 258 chars,
past MAX_PATH on Windows); the .ps1 works under a short
%SystemDrive%\ssm-<8hex> root and falls back to rd /s /q on cleanup.
Pinned output hashes unchanged (rebuilt every target).
- build-ssm-plugin.sh: the header no longer claims a git commit-id check.
- windows-verify-signatures.ps1: compare signer Subject + Issuer, not the
thumbprint (Artifact Signing certificates rotate); require
THIRD_PARTY_NOTICES in the MSI.
- windows-sign.ps1: allowlist exactly
src-tauri\binaries\session-manager-plugin-x86_64-pc-windows-msvc.exe.
- macOS jobs: check the .app carries the two-slice plugin and
Contents/Resources/THIRD_PARTY_NOTICES.
- CLAUDE.md: a local release build must re-run the build script.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AWS ships its prebuilt plugin as "AWS Content" under the AWS Customer
Agreement; the source is Apache-2.0. Replace the binary fetch with
scripts/build-ssm-plugin.sh (any triple, cross-compiles; universal via
lipo) and build-ssm-plugin.ps1 (Windows runner):
- source: tag 1.2.896.0 at commit 6430675a, GitHub archive SHA-256
checked before extraction;
- Go 1.26.11 from go.dev, published SHA-256 checked before use;
- the repo's own build (GOPATH mode, vendored deps, -s -w,
sessionmanagerplugin-main) with VERSION stamped to the tag, plus
-trimpath, no VCS stamp, empty build id, CGO off;
- output must equal a pinned SHA-256 per target (reproducible builds).
Each platform job builds its own targets. Windows: the exe is now ours
and unsigned, so windows-sign.ps1 allowlists it and
windows-verify-signatures.ps1 requires it signed by the installer's own
certificate in the MSI and NSIS. THIRD_PARTY_NOTICES now carries the
source's LICENSE/NOTICE/THIRD-PARTY, the commit, every linked vendored
module's licence and Go's. AWS's GPG key and the AWS-signature checks
are gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>