agentworth 0.1.11 → 0.1.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/lib/resolver.js +9 -8
  2. package/package.json +1 -1
package/lib/resolver.js CHANGED
@@ -35,9 +35,10 @@ export function getTargetTriple(platform = process.platform, arch = process.arch
35
35
  // Windows dropped 2026-09-02: release.yml no longer builds x86_64-pc-windows-msvc, so
36
36
  // this would 404 against the downloader even if it matched. The recurring failure was
37
37
  // GNU tar on Windows misparsing a "C:\..." archive path as a remote "host:path" tar
38
- // spec -- fixable (--force-local), but broke across multiple releases regardless, and
39
- // nobody here can test a real Windows box to catch it before it ships. A user who wants
40
- // this on Windows can still build it themselves: `cargo build --release -p agentworth-cli`.
38
+ // spec -- no clean fix ever stuck (a --force-local attempt just broke macOS's BSD tar
39
+ // instead), and nobody here can test a real Windows box to catch it before it ships. A
40
+ // user who wants this on Windows can still build it themselves: `cargo build --release
41
+ // -p agentworth-cli`.
41
42
  return null;
42
43
  }
43
44
 
@@ -254,12 +255,12 @@ export async function downloadAndExtractBinary(options = {}) {
254
255
 
255
256
  await downloadFile(url, archivePath);
256
257
 
257
- // Extract archive. --force-local matters on Windows: a drive-letter path like
258
- // "C:\Users\...\agentworth.tar.gz" otherwise gets parsed as a "host:path" remote-tar
259
- // spec (the "C" before the colon reads as a hostname), and tar tries to rsh/ssh to it
260
- // instead of opening a local file.
258
+ // No --force-local here: it was a Windows-only GNU tar workaround, and Windows
259
+ // support was dropped in 8b837c3. BSD tar (macOS's default) doesn't recognize
260
+ // the flag and fails every extraction with it present -- v0.1.11 shipped this
261
+ // exact break. Keep it off; there's no platform left where it does anything.
261
262
  try {
262
- execFileSync('tar', ['--force-local', '-xzf', archivePath, '-C', cacheDir]);
263
+ execFileSync('tar', ['-xzf', archivePath, '-C', cacheDir]);
263
264
  } catch (err) {
264
265
  throw new Error(`Failed to extract ${archiveName}: ${err.message}`);
265
266
  } finally {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agentworth",
3
- "version": "0.1.11",
3
+ "version": "0.1.12",
4
4
  "description": "Discover, normalize, and understand AI-agent histories locally.",
5
5
  "type": "module",
6
6
  "main": "./lib/resolver.js",