apiPulse.app
This is a live demo. Register to save subscriptions and get email notifications.

Historical changes

2493 entries from demo-selected APIs

11-05-2026
Atlassian

[Added] Add and get suggested edits tools have been added to Confluence

Rollout : progressive rollout by tenant. IN PROGRESSWe’re excited to announce that the below Confluence suggested edits tools have been added to Confluence on Atlassian MCP. Users who have previously approved access to the respective toolsets will start to see availability of these tools shortly as the feature is progressively rolled out.write_confluence:addConfluenceContentSuggestionsread_confluence:getConfluenceContentSuggestionsFor details on this tool and other tools available on Atlassian MCP, please refer to our Supported Tools.

Source
11-05-2026
Cloudflare

Durable Objects, Workers - Automatic retries for Durable Object calls

The runtime now retries fetch() and RPC calls to a Durable Object when they fail with a retryable error before reaching it. This applies whether the caller is a Worker or another Durable Object. Short disruptions, such as brief network interruptions, no longer need a retry loop in your code. By default, the runtime retries a call up to four times, and starts no retry more than 10 seconds after the initial call starts. It does not retry errors thrown by your Durable Object code, or errors with .overloaded set to true. If the connection drops and the runtime cannot tell whether the Durable Object received the call, it still retries, but the Durable Object rejects the retry if the first attempt arrived. A method never runs twice because of a retry, unless you mark it with retryable() from cloudflare:durable-objects: src/index.jsjsimport { DurableObject } from "cloudflare:workers"; import { retryable } from "cloudflare:durable-objects"; export class Cart extends DurableObject { static { retryable(this.prototype.setQuantity); } // Idempotent: a second run sets the same quantity. async setQuantity(itemId, quantity) { await this.ctx.storage.put(itemId, quantity); } // Not retryable: a second run would add another item. async addOne(itemId) { const quantity = (await this.ctx.storage.get(itemId)) ?? 0; await this.ctx.storage.put(itemId, quantity + 1); } }src/index.tstsimport { DurableObject } from "cloudflare:workers"; import { retryable } from "cloudflare:durable-objects"; export class Cart extends DurableObject { static { retryable(this.prototype.setQuantity); } // Idempotent: a second run sets the same quantity. async setQuantity(itemId: string, quantity: number): Promise { await this.ctx.storage.put(itemId, quantity); } // Not retryable: a second run would add another item. async addOne(itemId: string): Promise { const quantity = (await this.ctx.storage.get(itemId)) ?? 0; await this.ctx.storage.put(itemId, quantity + 1); } } To change the limits for one stub, pass a retry option to get() or getByName(). maxRetries accepts 0 to 10 retries, and timeoutMs accepts 500 to 60,000 milliseconds: src/index.jsjsconst stub = env.CART.getByName("user-123", { retry: { maxRetries: 1, timeoutMs: 2000 }, });src/index.tstsconst stub = env.CART.getByName("user-123", { retry: { maxRetries: 1, timeoutMs: 2000 }, }); If you already retry Durable Object calls in your own code, each of your attempts now includes the runtime's retries. Lower your own attempt count, or set maxRetries: 0 on stubs where your code handles retries. To use retryable() and the retry option, update to Wrangler 4.158.0 or later. For more information, refer to Automatic retries.

Source
11-04-2026
Amazon SP-API

November 4, 2026 SP-API Release

November 4, 2026 SP-API Release Notes are now available! For more information, refer to Release Notes.

Source
11-04-2026
Atlassian

[Announcement] Bitbucket 9.4.27 and 10.2.9 releases available now

Bitbucket Data Center and Server 9.4.27 and 10.2.9 bug fix releases are available now!To see the issues resolved in these bug fix releases, go to:Bitbucket Data Center and Server 9.4 release notesBitbucket Data Center and Server 10.2 release notesGet the latest LTS bug fix release

Source
11-04-2026
Claude

2.1.318

Added Added a record of your answer when Claude Code asks to turn on the mods it writes in a session Added assume_role on mantle upstreams of the Claude apps gateway, for a role in another AWS account and for per-developer AWS cost attribution Added an effort option to a mod's $.model.fork, so a quick side job can run at low whatever effort the session uses; the result reports the effort sent Added the date a stored claude.ai sign-in ends to claude auth status (loginExpiresAt) and to claude -p JSON results (credential_expires_at) Added a one-line stderr warning to claude -p text output, starting 10 days before a stored claude.ai sign-in ends Gateway: Added a log warning when the Google access token from a federation (external_account) credentials file is about to expire Self-hosted runner: Added CLAUDE_RUNNER_SPAWN_REASON to the orchestrator's spawn-runner hook environment: why Anthropic sent the request (e.g. runner_lost, resumed); unset when none was sent Self-hosted runner: Added a startup warning when --release-idle-session-min is the last argument with no value (still ignored) or has a value of only spaces (still read as 0) [Cloud sessions] Added a No repository option: a cloud session on an Anthropic-hosted environment can now start without picking a repository [Cloud sessions] Added the usual Chrome names to cloud sessions, so tools other than Playwright can find the built-in Chromium through google-chrome and CHROME_PATH [Cloud sessions] Added a New session button to the card shown when a cloud session's environment was deleted, where the message box is hidden Changed Changed Claude Code to no longer install or update the IDE extension when started in an IDE terminal; use /ide from an outside terminal or your editor's extensions view Changed subagents to stop instead of switching models when "Switch models when a message is flagged" is set to "Ask each time" Changed background subagents to move a shell command to the background after 3 minutes on all providers, so the prompt cache doesn't expire while it runs Changed subagent progress summaries on Bedrock, Vertex, Foundry, or with telemetry off: on a cold prompt cache, one can now wait up to 5 minutes for the subagent's pending response Changed what a mod attaches at prompt.submit to stay in the user's turn rather than go out as a system message Changed deniedMcpServers URL entries to also block Anthropic-provided servers whose upstream URL matches, and connectors in cloud sessions and on self-hosted runners, where the session is given the connector's own URL; otherwise deny a connector by name Changed the /permissions rule details, built-in rules and delete confirmation views to use the standard dialog; pressing Ctrl+C twice there now goes back or cancels instead of quitting Changed /claude-api managed-agents-onboard to give a new agent's built-in tools, and a quickstart template's MCP tools, the auto permission policy ("Judge risky actions") by default, matching the Claude Console; say "run without asking" to opt out Removed the 2.1.288 fix that kept the model's earlier thinking when resuming a conversation started on 2.1.286 or earlier; that thinking can now be dropped Self-hosted runner: Changed the orchestrator's log lines: ok session=… now prints at every log level on stdout (was debug only, stderr) with reason=… after jti=…, and nack session=… ends its fields with reason=… after retryable=…; update scripts that match retryable=true: or retryable=false: [Cloud sessions] Changed connector search results to tell Claude that the search covers only part of the connector directory

Source
11-04-2026
Cloudflare

AI Gateway - Route across a pool of models with model aliases

AI Gateway now supports model aliases. A model alias is a pool of models that your application calls by one name, such as custom/support-fast. AI Gateway tries the models in the order you set and falls back to the next one if a request fails, or uses smart routing to choose a model for each request. Because your application only references the alias, you can swap models or change the routing algorithm on your gateway without redeploying. Create and manage aliases on your gateway's Routing page, alongside dynamic routes. To call an alias through the REST API, use its name as the model. For example, send this body to /accounts/{account_id}/ai/run: { "model": "custom/support-fast", "input": { "messages": [{ "role": "user", "content": "Reply with a short greeting." }] } } Include the cf-aig-gateway-id header to select the gateway where you created the alias. Aliases are scoped to individual gateways. For setup instructions and routing options, refer to Model aliases.

Source
11-04-2026
Cloudflare

Bots - Granular access controls for the top Personal Agents

The Configure AI bot policies setting is now named AI Crawler and Agent access policies. Personal agents act on a person's behalf, fetching information or browsing in response to a request. The updated policies let you set actions for the top Personal Agents individually. This gives you control over agent access while allowing visitors to use agents to find answers or compare products using your site's content. Customize how Personal Agents access your site via Security > Settings > AI Crawler and Agent access policies. For more information, check out our blog ↗︎ or refer to our documentation for AI Crawler and Agent access policies.

Source
11-04-2026
Cloudflare

Browser Isolation, Cloudflare One - Block data entry with Browser Isolation without losing search, copy, and zoom (beta)

Isolation policies now support a third keyboard option in beta: Allow read-only actions. Previously, the keyboard setting was binary — allow all input or block everything. With Allow read-only actions, you can block data entry while preserving the built-in browser actions your users depend on. In Allow read-only actions mode, users can still find in page, select all, copy, print, and zoom. All other keyboard input is blocked from reaching the isolated page. Copy and print remain subject to their own policy settings, so the controls compose instead of overriding each other. For example, setting the keyboard to Allow read-only actions and copy to Do not allow lets users search and zoom but prevents them from copying content. To use this feature, set Keyboard to Allow read-only actions in your isolation policy settings. Via the API, set keyboard to enable_read_only_actions in the biso_admin_controls object with version set to v2. For more information, refer to Keyboard.

Source
11-04-2026
Cloudflare

Cloudflare Network Firewall - New managed rule to help mitigate CVE-2026-98432.

Cloudflare Network Firewall has a new managed rule to help mitigate the Linux IPv4 TCP use-after-free vulnerability (CVE-2026-98432 ↗︎): Rule name: Block CVE-2026-98432 traffic Rule ID: 6a4df2bf984946a88c74b07349557e83 The rule is disabled by default. To use it: Go to Networking > Firewall Policies > Managed Rulesets. Enable the rule with action Log first. Review traffic that matches the rule. If the matching traffic is not expected for your environment, change the action to Block. For more information on enabling managed rulesets, refer to Enable managed rulesets. For more details about the vulnerability, including an agent assessment prompt and evidence sources, refer to the Cloudflare Radar Zero Wire briefing ↗︎.

Source
11-04-2026
Cloudflare

Load Balancing, Cloudflare Tunnel, Cloudflare Mesh - Steer Cloudflare One users and private networks to the same endpoint with session affinity and hash steering in private load balancers

Private load balancers can now keep each user on the same endpoint. This helps with applications that keep session state on a single server. Cloudflare One Client or Cloudflare WAN siteConnects to 100.112.0.0Private load balancerPicks a healthy endpoint based on your steering policyHealth monitorsSteeringSession affinityPool 1Cloudflare Tunnel10.0.0.1vnet-aPool 2Cloudflare Mesh node10.1.0.1defaultPool 3Cloudflare WAN10.2.0.1defaultEndpoint = IP address + virtual network Two options are available: Hash endpoint steering. In the dashboard, set a pool's Endpoint steering to Hash. Each user is mapped to an endpoint within the pool. Session affinity. With the API, set session_affinity to ip_cookie on the load balancer. Each user stays on the same endpoint while it remains healthy and your pools do not change. Refer to Session affinity. For traffic from the Cloudflare One Client, Cloudflare identifies the user by their device, so a user stays on the same endpoint even if their IP address changes. For other traffic, such as from a Cloudflare WAN site, Cloudflare uses the source IP address. This works for endpoints reached through Cloudflare Tunnel, Cloudflare Mesh, and Cloudflare WAN. Affinity pins the endpoint, not the cloudflared or Mesh replica that carries the traffic. To learn how private load balancing fits with your connectors, refer to Load balance private network traffic.

Source
On demo you can only see one page. Register for full history and email notifications.