Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .agents/plugins/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
"source": {
"source": "url",
"url": "https://github.com/deriv-com/deriv-api-plugin.git",
"ref": "v1.0.13"
"ref": "v1.0.14"
},
"policy": {
"installation": "AVAILABLE",
Expand Down
2 changes: 1 addition & 1 deletion .antigravity-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
"name": "deriv",
"displayName": "Deriv",
"description": "Live Deriv API schemas, payload validation, and guides for authentication, subscriptions, trades, and errors.",
"version": "1.0.13",
"version": "1.0.14",
"logo": "./assets/logo.png",
"suggestedPrompts": [
"Look up the live schema for a Deriv API endpoint",
Expand Down
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
"source": {
"source": "url",
"url": "https://github.com/deriv-com/deriv-api-plugin.git",
"ref": "v1.0.13"
"ref": "v1.0.14"

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit · Catalogue refs pin v1.0.14 before the tag exists

Both marketplace pins point at tag v1.0.14, but that tag is only created after merge (per the PR's 'After merge' step; this promotion is a manual PR, not the publish.yml run that cuts tags). Failure scenario: between merge and tagging, or if the tag step is skipped, /plugin install deriv@deriv and codex plugin marketplace upgrade cannot resolve the ref, and installs fail for every user. This is the documented process, so it's a nit, but the tag step must not be missed.

Suggestion: Create the annotated v1.0.14 tag and the release immediately after merge, as the PR describes, and confirm both refs resolve.

},
"displayName": "Deriv",
"homepage": "https://developers.deriv.com",
Expand Down
2 changes: 1 addition & 1 deletion .claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "deriv",
"displayName": "Deriv",
"version": "1.0.13",
"version": "1.0.14",
"description": "Live Deriv API schemas, payload validation, and guides for authentication, subscriptions, trades, and errors.",
"author": { "name": "Deriv", "email": "api-support@deriv.com" },
"homepage": "https://developers.deriv.com",
Expand Down
2 changes: 1 addition & 1 deletion .codex-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "deriv",
"version": "1.0.13",
"version": "1.0.14",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit · Codex release_notes still says 'First directory release.'

The version moves to 1.0.14, but extensions.com.openai.publication.release_notes (.codex-plugin/plugin.json:105, outside the diff) still reads 'First directory release. …'. Failure scenario: a resubmission or upgrade of the Codex directory listing at 1.0.14 shows notes for the first release rather than this one (README Privacy and Support sections, author.url). verify-surface only checks that the field is non-empty, so CI won't catch it.

Suggestion: Update release_notes to describe the 1.0.14 changes in the next promotion.

"description": "Live Deriv API schemas, payload validation, and guides for authentication, subscriptions, trades, and errors.",
"author": {
"name": "deriv",
Expand Down
2 changes: 1 addition & 1 deletion .cursor-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "deriv",
"displayName": "Deriv",
"version": "1.0.13",
"version": "1.0.14",
"description": "Live Deriv API schemas, payload validation, and guides for authentication, subscriptions, trades, and errors.",
"author": { "name": "Deriv", "email": "api-support@deriv.com" },
"homepage": "https://developers.deriv.com",
Expand Down
18 changes: 18 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -157,6 +157,24 @@ server, so keep API tokens and other secrets out of tool-call arguments.
When you build an integration that itself calls the Deriv API, your own
application supplies its own credentials.

## Privacy

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit · Privacy section duplicates PRIVACY.md contact details

The new Privacy section copies the policy URL and the DPO contact (dpo@deriv.com) from PRIVACY.md, and repeats the PRIVACY.md pointer already in 'Where to go next' (lines 181-182). Failure scenario: if the DPO contact or policy URL changes, one of README.md, PRIVACY.md or the Codex privacyPolicyURL is easily missed, and the public README gives wrong privacy-contact information. The spec deliberately adds a direct link for Kiro's submission check, so this is a nit.


The [Deriv Privacy Policy](https://deriv.com/privacy-policy) applies to
personal data processed through the plugin. See [`PRIVACY.md`](PRIVACY.md) for
what the plugin and the hosted server process.

For privacy questions or requests, contact Deriv's Data Protection Officer at
[dpo@deriv.com](mailto:dpo@deriv.com).

## Support

- Questions and bug reports:
[GitHub issues](https://github.com/deriv-com/deriv-api-plugin/issues).
- Email: [api-support@deriv.com](mailto:api-support@deriv.com).

Report a suspected vulnerability privately, as [`SECURITY.md`](SECURITY.md)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit · Vulnerability-reporting route now described in three places

The Support section's vulnerability sentence repeats the SECURITY.md bullet in 'Where to go next' and CONTRIBUTING.md's 'Reporting a security issue' section. Failure scenario: a change to the private disclosure process has to be made in all three places, or they will contradict each other.

describes, not in a public issue.

## Where to go next

- [`CONTRIBUTING.md`](CONTRIBUTING.md) — how to file issues and open pull requests.
Expand Down
2 changes: 1 addition & 1 deletion kimi.plugin.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "deriv",
"version": "1.0.13",
"version": "1.0.14",
"description": "Live Deriv API schemas, payload validation, and guides for authentication, subscriptions, trades, and errors.",
"keywords": ["deriv", "trading", "api", "websocket", "rest", "options", "finance", "fintech"],
"author": { "name": "Deriv", "email": "api-support@deriv.com" },
Expand Down
4 changes: 2 additions & 2 deletions plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "deriv",
"description": "Live Deriv API schemas, payload validation, and guides for authentication, subscriptions, trades, and errors.",
"version": "1.0.13",
"author": { "name": "Deriv", "email": "api-support@deriv.com" },
"version": "1.0.14",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit · Release still hand-edits eight version/ref lines

Each promotion hand-edits six manifest versions and two marketplace refs (8 lines in this diff). Failure scenario: a missed one is caught only if verify-surface runs on that exact tree. Deriving all versions and refs from one value in the promotion build would remove this class of error. This lives in the private build tooling, so it's an optional improvement.

Suggestion: Generate manifest versions and catalogue refs from a single source in build-promotion-bundle.mjs.

"author": { "name": "Deriv", "email": "api-support@deriv.com", "url": "https://developers.deriv.com" },

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit · author.url added only to the root plugin.json

author.url is added to root plugin.json only. The Claude, Cursor, Kimi and Antigravity manifests still declare author without url. Failure scenario: hosts reading those manifests show no author link while Agent Plugins v1 hosts do. verify-surface checks author.url only on the Codex manifest, so further drift has no CI signal. The spec scoped the change to the root manifest, so this is a nit.

Suggestion: Consider adding the same author.url to the other manifests that accept it, or pin it in verify-surface.

"homepage": "https://developers.deriv.com",
"repository": "https://github.com/deriv-com/deriv-api-plugin",
"license": "MIT",
Expand Down
Loading