@openthink/stamp 2.0.0 → 2.0.1

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 (7) hide show
  1. package/README.md +4 -5
  2. package/dist/hooks/pre-receive.cjs.map +1 -1
  3. package/dist/index.js +295 -57
  4. package/dist/index.js.map +1 -1
  5. package/dist/server/stamp-review.cjs +4 -1
  6. package/dist/server/stamp-review.cjs.map +1 -1
  7. package/package.json +1 -1
package/README.md CHANGED
@@ -127,11 +127,10 @@ stamp attest --into main --push origin # signs the v4 attestation envelope + a
127
127
  # Reviewer's check goes green → human clicks merge in the GitHub UI
128
128
  ```
129
129
 
130
- > **2.0.1 note:** producer-side production of the extended v3+ PR-attestation
131
- > blob (AGT-355) is queued for 2.0.1. The verifier ships in 2.0 so the
132
- > contract is locked; until the producer ships, pin the GitHub Action to a
133
- > 1.x `stamp-version` input. See the migration guide for the bridge-window
134
- > guidance.
130
+ > **2.0.1:** server-side v3 PR-attestation production (AGT-355) ships in
131
+ > this release. `stamp attest` now folds server-signed approvals into a
132
+ > v3 envelope when the branch rule declares `review_server`; the GH
133
+ > Action accepts the envelope directly with no 1.x-action pin needed.
135
134
 
136
135
  The attestation is keyed on the **content** of the diff (`git patch-id`), so
137
136
  it survives every GitHub merge strategy: squash, rebase, and merge-commit