@tangle-network/agent-integrations 1.0.4 → 1.0.6
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.
- package/README.md +9 -1
- package/data/bundled-adapter-manifests.json +1 -1
- package/dist/{adapters-x5V_2d6D.js → adapters-yGJfP7bH.js} +174 -85
- package/dist/{adapters-x5V_2d6D.js.map → adapters-yGJfP7bH.js.map} +1 -1
- package/dist/{bundled-manifest-data-DLzwtr7z.js → bundled-manifest-data-CFwqe89k.js} +110 -7
- package/dist/{bundled-manifest-data-DLzwtr7z.js.map → bundled-manifest-data-CFwqe89k.js.map} +1 -1
- package/dist/connectors/adapters/index.js +1 -1
- package/dist/connectors/index.js +2 -2
- package/dist/index-C5W0VfzQ.d.ts.map +1 -1
- package/dist/index.js +4 -4
- package/dist/internal/bundled-manifest-runtime.js +1 -1
- package/dist/mcp.js +1 -1
- package/dist/registry.js +1 -1
- package/dist/{specs-BQHb_KgP.js → specs-Ci6L1t37.js} +2 -2
- package/dist/{specs-BQHb_KgP.js.map → specs-Ci6L1t37.js.map} +1 -1
- package/dist/specs.js +1 -1
- package/dist/{src-BZmlzQzN.js → src-Dy0n71_S.js} +3 -3
- package/dist/{src-BZmlzQzN.js.map → src-Dy0n71_S.js.map} +1 -1
- package/dist/triggers/index.d.ts +20 -1
- package/dist/triggers/index.d.ts.map +1 -1
- package/dist/triggers/index.js +183 -14
- package/dist/triggers/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -470,7 +470,7 @@ The test suite packs the npm artifact and bundles `/worker`, `/specs`, and
|
|
|
470
470
|
|
|
471
471
|
Feature PRs must leave the package version and `CHANGELOG.md` unchanged.
|
|
472
472
|
After features merge, run the **Prepare Release** workflow and choose a patch, minor, or major bump.
|
|
473
|
-
The workflow uses Node and Git to open a `release/v<version>` PR from current `main`.
|
|
473
|
+
The workflow reads the stable npm predecessor and uses Node and Git to open a `release/v<version>` PR from current `main`. An unpublished tag does not become the changelog baseline. Compatible releases after 1.0 use a patch; the shared archive admission check decides whether a change requires a major.
|
|
474
474
|
It does not install dependencies or publish a package.
|
|
475
475
|
|
|
476
476
|
Review that the release branch version matches the next package version.
|
|
@@ -486,3 +486,11 @@ Confirm that the published archive installs and its intended consumer flow works
|
|
|
486
486
|
## License
|
|
487
487
|
|
|
488
488
|
MIT
|
|
489
|
+
|
|
490
|
+
### Drive change-feed triggers
|
|
491
|
+
|
|
492
|
+
`google-drive.file.changed` reads metadata and removals through `get_start_page_token` and `list_changes`, using the existing `drive.readonly` grant. It does not request document contents or create watch channels. Its first poll obtains the current change-feed position; later polls consume one bounded page in provider order, independent of timestamp ties.
|
|
493
|
+
|
|
494
|
+
Hosts keep `HostedTriggerCursor.state` opaque. Pass a durable `checkpoint(cursor)` callback to `pollHostedTrigger`: the Drive provider freezes each pending page there before returning events. Admit every event with its stable `id`, then persist the returned cursor only after all admissions succeed. On interruption, retry the checkpoint cursor; it replays identical events without rereading mutable metadata. A missing checkpoint sink, invalid cursor, incomplete continuation or malformed page fails without resetting the feed. Existing timestamp-based definitions and callers keep their prior behavior. See Google's [change-feed contract](https://developers.google.com/workspace/drive/api/guides/manage-changes).
|
|
495
|
+
|
|
496
|
+
Timestamp providers retain all admitted IDs at the active timestamp boundary and discard them only when the boundary advances. The retained-key bound lives in `MAX_BOUNDARY_KEYS` in the trigger runner; overflow fails explicitly with the prior cursor intact. These definitions remain limited by each provider's existing listing/history contract; they do not provide Drive's token-based feed guarantees.
|