deere-sdk 2.2.0 → 2.3.0

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 (3) hide show
  1. package/CHANGELOG.md +11 -0
  2. package/README.md +39 -0
  3. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -5,6 +5,17 @@ All notable changes to this project will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [2.3.0] - 2026-06-18
9
+
10
+ ### Changed
11
+ - Release artifacts are no longer cosign-signed; the `.tgz.sig` / `.tgz.pem` assets
12
+ are removed from GitHub Releases. Authenticity now comes from npm package provenance
13
+ (`npm audit signatures`) and GitHub build attestations (`gh attestation verify`,
14
+ online by default or offline via `--bundle`). A new "Verifying Releases" section in
15
+ the README documents both paths. This drops a brittle, redundant signing layer
16
+ (cosign v3 broke the legacy `sign-blob` flow, leaving the pipeline pinned to a
17
+ deprecated cosign v2 line); the npm package itself is unchanged.
18
+
8
19
  ## [2.2.0] - 2026-06-18
9
20
 
10
21
  ### Fixed
package/README.md CHANGED
@@ -820,6 +820,45 @@ gh workflow run release.yml --ref vX.Y.Z
820
820
 
821
821
  ---
822
822
 
823
+ ## Verifying Releases
824
+
825
+ Every release produces **two independently verifiable artifacts**, and they are not byte-identical: the package on the npm registry (built and published by `publish.yml`) and the `.tgz` attached to the GitHub Release page (built by `release.yml`). They verify differently. `npm audit signatures` checks the copy you installed from the registry; it does **not** verify a tarball downloaded from the Release page. Both chains trace back to Sigstore through GitHub's OIDC identity, so there is no separate signing key to manage.
826
+
827
+ ### The npm package (what `npm install` pulls)
828
+
829
+ ```bash
830
+ npm audit signatures
831
+ ```
832
+
833
+ Verifies the registry signature and the SLSA build-provenance attestation for your installed packages, including `deere-sdk`.
834
+
835
+ ### The GitHub Release tarball (the `.tgz` on the Release page)
836
+
837
+ ```bash
838
+ gh release download vX.Y.Z --repo ProductOfAmerica/deere-sdk --pattern '*.tgz'
839
+ gh attestation verify deere-sdk-X.Y.Z.tgz \
840
+ --repo ProductOfAmerica/deere-sdk \
841
+ --signer-workflow ProductOfAmerica/deere-sdk/.github/workflows/release.yml \
842
+ --source-ref refs/tags/vX.Y.Z
843
+ ```
844
+
845
+ `--source-ref` binds the check to the release tag. `--predicate-type` defaults to `https://slsa.dev/provenance/v1`, so it can be omitted. By default `gh attestation verify` fetches the attestation from GitHub's API (online).
846
+
847
+ ### Offline / air-gapped / mirrors
848
+
849
+ Fetch the Sigstore bundle once while online, then verify with no further API calls:
850
+
851
+ ```bash
852
+ gh attestation download deere-sdk-X.Y.Z.tgz --repo ProductOfAmerica/deere-sdk
853
+ gh attestation verify deere-sdk-X.Y.Z.tgz \
854
+ --bundle <downloaded-bundle>.jsonl \
855
+ --repo ProductOfAmerica/deere-sdk \
856
+ --signer-workflow ProductOfAmerica/deere-sdk/.github/workflows/release.yml \
857
+ --source-ref refs/tags/vX.Y.Z
858
+ ```
859
+
860
+ ---
861
+
823
862
  ## Disclaimer
824
863
 
825
864
  > **This is an unofficial SDK** and is not affiliated with, endorsed by, or connected to John Deere or Deere & Company.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "deere-sdk",
3
- "version": "2.2.0",
3
+ "version": "2.3.0",
4
4
  "description": "Unofficial TypeScript SDK for John Deere Operations Center API",
5
5
  "author": "ProductOfAmerica",
6
6
  "license": "MIT",