0.0.4

Changes

Diagnostics fix following a reported 412 error on the bulk-snippet-bom-entries PUT:

• Error visibility: GetResponse previously swallowed the response body on PUT failures (log.Fatalln before reading it), hiding Black Duck's actual error message. It now reads and prints the body so the real cause of failures like 412 is visible.
• Guard against invalid empty body: If no source-bom-entries match the given match string, the tool previously still sent a null JSON body to the PUT endpoint, which Black Duck rejects. It now fails fast with a clear message identifying the unmatched match string instead.

Binaries

• hubsm.exe - Windows amd64
• hubsm-amd64 - Linux amd64
• hubsm-arm64 - Linux arm64

0.0.3

Changes

Synced the client with the latest Black Duck REST API documentation:

• Bulk snippet BOM entries (PUT /bulk-snippet-bom-entries): bumped Accept/Content-Type media type from application/vnd.blackducksoftware.bill-of-materials-6+json to application/vnd.blackducksoftware.bill-of-materials-7+json. The API doc no longer documents v6 for this endpoint, only v7.
• Output model: added optional origin field to snippetBomComponentRequests[] (URL of the component version origin), matching the v7 request schema.
• Scan summary representation: added aiModelMatchCount (required) and errorCode (optional) fields, present in the current API but missing from the model.

Verified unchanged: authentication (user-4+json) and scan-summaries listing (scan-6+json) media types/response shape still match the current API.

Binaries

• hubsm.exe - Windows amd64
• hubsm-amd64 - Linux amd64
• hubsm-arm64 - Linux arm64

0.0.2

Hub bulk snippet matcher arm64 binary added for linux

0.0.1

initial release
hubsm is a linux variant hubsm.exe is for windows both are for amd64 arch