Update publication

Outcome

Updates the destination name, base URL, description and SEO defaults while retaining its existing slug. It does not provision hosting or rewrite existing immutable article snapshots and canonical URLs.

Before you start

• Verify identity and the intended environment with topolo whoami before selecting an explicitly authorized organization.
• Discover the published workspace:write permission.
• Discover an accessible Blog workspace and set WORKSPACE_ID to that exact returned id. Pass workspace binding separately from action input.
• Review the actual state change and confirm the unchanged plan before execution. Fixture ids and provider responses grant no live authority.

Discover the target

topolo whoami --json
topolo actions get app_topolo_blog.publications.update --detail --json
topolo workspaces list topolo-blog --json

• publicationId: Exact destination id from publications.list or publications.create; a display name or slug is not an id.

Request

PATCH /api/publications/{publicationId}

Inspect parameters and test this action.

Input fields

Worked examples

Documentation source snapshot: TopoloBlog 80d6961207a4ca688b7e9edb947dda720051ad32 (tree 534a285e739a27c1ea9e2c187ce8863824f6c590). The examples retain local fixture captures labeled baseline 2c64c35bf291a47bb3a0c597dcea46ccb47e2a08; their exact executed working tree is not established here. They were not rerun at this documentation snapshot. The production catalog marker topolo.app.json is not a deployed worker revision. Recovery metadata read-back on 18 October 2026 associates the current production Blog API and web deployments with this source through the 17 October release receipt. This establishes applicable deployed source; it does not make these examples current production captures.

Actual exported Blog Worker, local Miniflare D1/R2 and all committed migrations. Auth, Insights, DNS, Cloudflare for SaaS, error reporting, queue and scheduled-workflow boundaries are synthetic and outbound fetch is sealed. No deployed provider, delivery or scheduled execution outcome is established. English examples use the packaged test translation release; article checks and widget labels follow the verified request locale. No live translation release is proved by this fixture.

Save a reviewed input as payload.json. Replace fixture identifiers using discovery in the authorized context.

topolo actions validate app_topolo_blog.publications.update --data @payload.json --json
topolo actions plan app_topolo_blog.publications.update --resource-type workspace --resource-id "$WORKSPACE_ID" --data @payload.json --confirm --json
topolo actions call app_topolo_blog.publications.update --resource-type workspace --resource-id "$WORKSPACE_ID" --data @payload.json --confirm --detail --json

MCP uses the same reviewed input. Replace the synthetic workspace resourceId through discovery when a binding is shown:

{
  "tool": "topolo_prepare_action",
  "arguments": {
    "actionId": "app_topolo_blog.publications.update",
    "input": {
      "publicationId": "publication_46dd8843-4fa4-4d2b-83a2-a9ac40b7e572",
      "name": "Updated publication",
      "baseUrl": "https://example.com/updates"
    },
    "resourceType": "workspace",
    "resourceId": "ws_blog_fixture",
    "confirm": true
  }
}

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_blog.publications.update",
    "input": {
      "publicationId": "publication_46dd8843-4fa4-4d2b-83a2-a9ac40b7e572",
      "name": "Updated publication",
      "baseUrl": "https://example.com/updates"
    },
    "resourceType": "workspace",
    "resourceId": "ws_blog_fixture",
    "confirm": true,
    "detail": true
  }
}

Successful response · HTTP 200

Input · payload.json:

{
  "publicationId": "publication_46dd8843-4fa4-4d2b-83a2-a9ac40b7e572",
  "name": "Updated publication",
  "baseUrl": "https://example.com/updates"
}

Source-reviewed illustration (retained local fixture response; not a current production capture):

{
  "publication": {
    "id": "publication_46dd8843-4fa4-4d2b-83a2-a9ac40b7e572",
    "organizationId": "org_blog_fixture",
    "workspaceId": "ws_blog_fixture",
    "name": "Updated publication",
    "slug": "fixture-publication",
    "baseUrl": "https://example.com/updates",
    "description": "",
    "defaultSeoTitle": null,
    "defaultSeoDescription": null,
    "isDefault": false,
    "articleCount": 0,
    "createdAt": "2026-10-06T07:31:32.374Z",
    "updatedAt": "2026-10-06T07:31:33.628Z"
  }
}

Call app_topolo_blog.publications.get and confirm the base URL is what you intended before linking to it.

Refused request · HTTP 401 · auth_error

Input · payload.json:

{
  "publicationId": "publication_46dd8843-4fa4-4d2b-83a2-a9ac40b7e572",
  "name": "Updated publication",
  "baseUrl": "https://example.com/updates"
}

Source-reviewed illustration (retained local fixture response; not a current production capture):

{
  "error": "Authentication token required"
}

Sign in again in the intended environment using a valid credential. Preserve the returned handler message; SDK auth_error can represent several authentication refusals.

Verify the result

• Call app_topolo_blog.publications.list and locate the returned publication id. Compare the name, baseUrl, description, defaults and retained slug. Inspect any existing article routing separately before changing public links.

Errors and recovery

• HTTP 401 · auth_error: Sign in again in the intended environment using a valid credential. Preserve the returned handler message; SDK auth_error can represent several authentication refusals.

Inspect the raw handler error as well as the SDK code. These examples establish observed local refusals, not every possible provider failure.

Recovery boundary

Read and retain the previous complete publication fields before updating. Restore those values with app_topolo_blog.publications.update and verify through app_topolo_blog.publications.list.

Evidence

Actual exported Blog Worker, local Miniflare D1/R2 and all committed migrations. Auth, Insights, DNS, Cloudflare for SaaS, error reporting, queue and scheduled-workflow boundaries are synthetic and outbound fetch is sealed. No deployed provider, delivery or scheduled execution outcome is established. English examples use the packaged test translation release; article checks and widget labels follow the verified request locale. No live translation release is proved by this fixture.

Documentation history

18 October 2026: Architecture reviewed the retained action guide against the pinned source declaration and named implementation boundaries, qualified local-capture provenance, and prepared paired human and agent amendments. This review does not record a product release, new fixture execution or publication.

2026-10-18: Architecture accepted the paired coauthor delta and qualified the current 80D deployment association from existing Recovery evidence. Examples remain source-reviewed retained-fixture illustrations; no new execution or guide publication is recorded.