You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v0.2.0 — Plugin HTTP contract and marketplace publish
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
Versioned plugin HTTP contract (version 1). Endpoint and webhook handlers can read the exact request bytes as req.rawBody (Uint8Array), the host-resolved req.clientIp, and req.httpContract. Return httpResponse(status, body, { headers, format }) to send a real HTTP status; the helper rejects invalid statuses, header injection, duplicate headers, transport headers and Set-Cookie. Ordinary returned objects keep their meaning as JSON data (#25). See docs/http-contract.md.
esc-plugin publish CLI for marketplace artifacts: SHA-256 tarball digest, optional RSA-SHA256 signature, S3-compatible upload or --artifact-uri, then registration with Escalated Cloud (#9).
No existing plugin code needs to change: the new request fields are optional and ordinary return values behave as before.
Signature verification must use req.rawBody. Never re-serialize req.body to check a signature. Handlers that verify signatures should reject requests without rawBody (older hosts do not send it).
rawBody, clientIp and httpResponse envelopes only work when the host bridge and @escalated-dev/plugin-runtime both support HTTP contract version 1 (runtime v0.2.0 advertises http_contract_versions: [1]).
The package version moves from 0.1.x to 0.2.0. Consumers pinning ^0.1.0 must widen the range to pick it up; git-ref installs can use the v0.2.0 tag.