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

Historical changes

2571 entries from demo-selected APIs

11-16-2026
Atlassian

[Announcement] Update Forge app scopes for UI Modifications on JSM Portal

What's changing We’re updating the scope requirements for the jira:uiModifications module when it runs on Jira Service Management (JSM) Portal request-create forms. Currently, apps running in this view may rely on Jira-specific scopes. From December 15, 2026, apps must explicitly declare JSM-specific scopes to continue executing UI Modifications on the JSM Portal. What you need to do To ensure your app continues to work without interruption, you must add either the classic scope set or the granular scope set to your manifest.yml file. You do not need both. Option 1: Classic scopespermissions: scopes: - read:servicedesk-request - write:servicedesk-requestOption 2: Granular scopespermissions: scopes: - read:servicedesk:jira-service-management - read:requesttype:jira-service-management - read:request:jira-service-management - write:request:jira-service-management - read:user:jiraMerge your chosen scopes into your existing manifest.yml permissions.Deploy the updated version of your app.Complete any required installation upgrades before December 15, 2026.If your app also supports Jira views (such as the issue view or issue create modal), ensure you retain the Jira-specific scopes required for those views. These JSM Portal requirements are additional and do not replace existing Jira scope requirements What happens if you don’t update? From 15 Dec 2026, UI Modifications will not execute on JSM Portal request-create forms unless the app declares one of the complete scope sets above. Declaring only the previously accepted Jira scopes will no longer be sufficient for JSM Portal.

Source
11-16-2026
Cloudflare

Artifacts, Workers - Artifacts now supports local development

You can now develop and test Artifacts locally. Create repos, import Git repositories over HTTPS, issue repo tokens, and clone or push with Git on your machine before deploying to Cloudflare's global network. Local repos are separate from your deployed repos, so you can test changes without affecting production data. Local repos also emit the same Artifacts events as production when a repo is created, imported, forked, or deleted, or when a repo token is created or revoked. This lets you test the Workflows that react to them before you deploy. To use local repos when you run your Worker locally, add an Artifacts binding to your Wrangler configuration file: { "$schema": "./node_modules/wrangler/config-schema.json", "name": "artifacts-worker", "main": "src/index.ts", // Set this to today's date "compatibility_date": "2026-11-16", "artifacts": [ { "binding": "ARTIFACTS", "namespace": "default" } ] }name = "artifacts-worker" main = "src/index.ts" # Set this to today's date compatibility_date = "2026-11-16" [[artifacts]] binding = "ARTIFACTS" namespace = "default" Run npx wrangler dev, then use the binding the same way you would in production: const created = await env.ARTIFACTS.create("starter-repo"); return Response.json({ remote: created.remote, token: created.token, });const created = await env.ARTIFACTS.create("starter-repo"); return Response.json({ remote: created.remote, token: created.token, }); The returned remote points to your local dev session, so you can use it with a standard Git client to clone and push. Local development requires the latest version of Wrangler and Git 2.32 or later on your PATH. When you develop with npx wrangler dev, the Cloudflare Vite plugin, or the Workers Vitest integration, Artifacts bindings use the local simulator by default. To use your deployed repos instead, set remote = true on the binding. To learn more, refer to Local development.

Source
11-16-2026
Cloudflare

Cloudflare One, Gateway - Cloudflare One adds Periodic Beaconing Traffic detection

Cloudflare One now includes Periodic Beaconing Traffic as a risk behavior. It analyzes Gateway HTTP traffic for regular check-ins to the same destination. Cloudflare flags a user after more than 30 contacts to the same destination in six hours. Contacts must be evenly spaced, from 10 seconds to about 12 minutes apart. Few other users in your organization contact that destination. Detection uses traffic behavior only. It does not use threat intelligence, categories, or reputation. Malware can check in with a command-and-control (C2) server this way, but legitimate software also checks in regularly. Treat each event as a lead to investigate, not proof that a destination is C2. By default, the behavior is off and its risk level is Info. To turn it on, go to Risk score > Risk behaviors. Cloudflare reports a continuing beacon once. Events usually arrive 3 to 6 hours after the six-hour window closes. Periodic Beaconing Traffic is available on Enterprise plans.

Source
11-15-2026
Atlassian

[Deprecation Notice] Deprecating the roles field in the Get user role assignments API

We’re replacing the roles response field with roleAssignments, which identifies each role and how it was assigned.What’s ChangingThe roles response field in the Get user role assignments API is deprecated and will be removed on May 15, 2027. We’re replacing the roles field with roleAssignments, which identifies each role and how it was assigned (for example, directly, through group membership, or inferred). The roleAssignments field is already available for use. The roles field will remain available throughout the deprecation period.What you need to doUpdate your integrations before May 15, 2027 to read role IDs from roleAssignments[].role instead of roles[].Identify where your integration reads the roles property from the API response.Update your code to read the role property within the roleAssignments array instead.For example, replace reading:"roles": [ "atlassian/user-access-admin" ]with reading the role property in:"roleAssignments": [ { "role": "atlassian/user-access-admin", "roleAssignmentMethods": ["group_direct"] } ]If your integration already uses roleAssignments, no action is required.

Source
11-13-2026
Atlassian

[Added] New jira:entityPropertySet module for bundling unlimited entity properties

What's newA new jira:entityPropertySet module type is now available for Forge apps. It lets you bundle multiple entity properties under a single module, with no limit on the number of properties. Why it mattersPreviously, each entity property required its own jira:entityProperty module, with a maximum of 100 indexable values per app. The new jira:entityPropertySet module removes this limit — apps can now declare hundreds or thousands of entity properties under a single module.How to use itDeclare the module in your manifest.yml:modules: jira:entityPropertySet: - key: my-properties properties: - propertyKey: stats entityType: issue values: - path: comments type: number searchAlias: commentCount - propertyKey: metadata entityType: issue values: - path: category type: string searchAlias: metaCategoryKey detailsJQL search via searchAlias works the same wayRequired permissions: read:jira-work and write:jira-workPlatform-wide limit of 1,000 searchable entity properties per entity type, shared across all apps on the tenantDocumentationjira:entityPropertySet module referenceRelatedFRGE-2171

Source
11-13-2026
Claude

2.1.325

Added Added a spinner tip in VS Code and similar integrated terminals about re-running a notebook cell, shown once Claude has read or edited a Jupyter notebook Added a line under the error shown when your organization's policy blocks a request, saying how to continue: run /rewind and change the message, or run /clear Added a note for Claude when a sandboxed git checkout, git stash or autostash pull cannot update protected files such as those in .claude [VSCode] Added prompt suggestions wherever the terminal shows them: Tab accepts the suggested next prompt; promptSuggestionEnabled: false in Claude Code's settings.json turns them off [VSCode] Added a Console sign-in that creates no API key [VSCode] Added a field to paste the redirect URL when signing in to an MCP server from the panel in SSH, WSL and container windows Changed Changed sandboxed Bash commands to follow the normal permission flow by default; set sandbox.autoAllowBashIfSandboxed: true to keep running them without prompts Changed managed settings that turn the sandbox on: to keep commands running without prompts, set sandbox.autoAllowBashIfSandboxed: true in your highest-ranking managed source Changed read-only git commands to ask first in a repository that isn't the project's or one you trusted; name it with --add-dir, not the additionalDirectories setting, to run them without prompts Changed scheduled tasks and /loop to ask before running a skill that declares allowed-tools or hooks; add Skill(name) to permissions.allow to run it unattended Changed "Always allow" in Desktop, IDE and SDK hosts: a rule alone is offered only when saving it would allow that command again, so a scheduled task that relied on one can now wait for you Changed the sandbox to refuse sandboxed writes to .claude settings, skills, agents, commands and hooks in added directories, as it does in the launch folder Changed worktree isolation: an isolated worktree session or agent is now refused git bisect run, git maintenance register|start and scalar's set-up commands, and is told what still works Changed plugin MCP bundles (.mcpb, .dxt) to unpack under the plugins directory, not .mcpb-cache in the plugin's folder, so read-only plugin folders load; one fetched by URL downloads again once Changed plugins of a remote marketplace that managed settings declare, enable and list in prependPlugins or appendPlugins to count as the organization's; pluginDigests is deprecated and ignored Changed plugin loading to skip, and claude plugin validate to report, some unsafe paths and links in a plugin's folder Changed nested skill loading: .claude/skills folders in --plugin-dir plugins no longer load from a session started above them; start Claude Code in the plugin folder instead Changed EnterWorktree to refuse a WorktreeCreate hook path that goes through a symlink inside the project; have the hook print the real path Changed tmux and iTerm2 teammates, and new sessions from the agents view opened with ←, to start in the session's folder instead of where the shell last ran cd Changed prompt suggestions in the terminal to refresh less often after 8 turns in a row started by background or scheduled tasks, saving usage until you press a key or return to the terminal Changed Esc on a background MCP task's question to "answer later": nothing is sent to the server, and the question stays in /tasks Changed CLAUDE_CODE_MAX_CONTEXT_TOKENS to also set the context window of unrecognized model IDs that start with claude-, such as a gateway's claude-sonnet-latest Changed /login to ask for permission to change your privacy settings Changed /cost, $.session.usage(), --max-budget-usd and the cost and token metrics to count a mod's $.model.complete and $.model.classify calls Changed the programs that Claude Code's sandbox starts for its own use, such as its network bridge, to run without Claude Code's sign-in tokens and API keys in their environment Changed ripgrep, local git commands and the sandbox runtime's own helper programs to run without the mTLS client key's passphrase in their environment Remote Control: Changed /resume and /teleport to disconnect first when the connected session has a share link, or when that can't be checked; run /remote-control to connect again Changed Claude Code on the web, cloud scheduled tasks and Cowork cloud sessions to start despite sandbox.failIfUnavailable: the hosted container has no command sandbox Changed requests for settings, permission rules, hooks or status over a cloud or self-hosted session's connection to return less or be refused; what applies in the session is unchanged Changed claude -p with no cached account data to wait for that data before its first request, so a first run in a clean environment can start a few seconds later Changed Claude's instructions to keep files you'll want out of its temporary scratchpad folder, which can be cleared Changed marketplace ref to accept the full ID of any commit on a branch or tag; clients before this version can't clone such a pin, so a marketplace pinned this way stops loading there Changed plugin marketplace and plugin downloads to use a CONNECT tunnel when ALL_PROXY is the only proxy set; a proxy that refuses CONNECT now fails them Changed -p and SDK runs in a worktree or submodule mounted into a container to apply .claude/settings.local.json allow rules only once the folder is trusted Changed self-hosted runners to refuse a session whose session folder or repository path is a symbolic link, other than a checkout hook's checkout Removed "ask your admin to raise it" from spend limit and shared budget errors in cloud sessions and under Remote Control [VSCode] Changed the install link's marketplace confirmation button to "Trust marketplace and continue"

Source
11-13-2026
Cloudflare

Browser Run - Browser Run Quick Actions now work in local development

You can now test Browser Run Quick Actions locally. Under npx wrangler dev, the browser binding's .quickAction() method runs against a Chrome instance on your machine. Before, .quickAction() worked only in remote mode, and local calls failed with The RPC receiver does not implement the method "quickAction". NoteThere are currently two limitations in the local simulation: The json action is emulated. It requires an AI model to extract data, and the model is not available locally, so the action returns placeholder data that matches your schema. The Kitesurf browser is not supported yet. For details, refer to Test Quick Actions locally.

Source
11-13-2026
Atlassian

[Announcement] External sites policy now applies to the Atlassian MCP server

The Atlassian Guard external sites policy now applies when your managed users connect to Atlassian sites through the Atlassian MCP server. You can block external Atlassian sites or allow only selected partner sites, while your own organization’s sites stay available. There’s no separate MCP setting to turn on.To get started with this changeGo to Atlassian Administration. Select your organization if you have more than one.Select Security, then Device security, then External sites.Create a draft policy that allows specific external sites or blocks all external sites.Activate the policy.If you already have an active external sites policy, it now applies to MCP. You don’t need to do anything. The policy requires Atlassian Guard Standard. Learn more: Manage access to external sites.

Source
11-13-2026
Atlassian

[Announcement] Connect service accounts to the Atlassian MCP server with OAuth 2.0

Organization admins can now let service accounts connect to the Atlassian MCP server using OAuth 2.0 client credentials. Pipelines and scheduled jobs get an access token without a browser sign-in, and you don’t need to turn on API token authentication for your organization.To get started with this change:In Atlassian Administration, select your organization if you have more than one.Go to Directory, then Service accounts, and create a service account. Give it app roles only on the sites it needs.Select the service account, then Create credentials and OAuth 2.0.Select the Product *:agent-interface scopes, plus read:me and read:account. You can’t change scopes after you create the credential.Copy the client ID and client secret. The secret is shown only once.In your workflow, exchange the client ID and secret for an access token, then send it to https://mcp.atlassian.com/v2/mcp as a Bearer token. Access tokens are valid for 60 minutes, so request a new one before the current one expires.To create the credential, see Create an OAuth 2.0 credential for service accounts.

Source
11-13-2026
Atlassian

[Announcement] Coming soon: neutral selected states, lighter headings and subtler search inputs

We’re introducing a set of visual refinements to Atlassian UI to reduce visual noise and make interfaces feel calmer and easier to scan. These changes are behind the platform-dst-tokens-finesse feature flag and will be enabled as part of the upcoming rollout, and we’re sharing an early heads-up so you can prepare your apps.Attached fileWhat’s changing?Neutral selected states: Selected backgrounds will move from blue to a neutral fill, keeping selections clear while reducing competing emphasis. Keyboard focus indicators will remain blue. Attached file Lighter headings: ADS heading weights will change from Bold (653) to Semibold (600), creating a lighter appearance. Attached file Subtler search inputs: Search inputs will have lighter borders, with slightly darker placeholder text and search icons for improved legibility. Attached file What should Marketplace partners review?Please review how your app’s UI sits alongside these changes, particularly where you use custom styling or override ADS defaults:Selected states: Review hardcoded blue backgrounds and custom overrides. Use semantic selection tokens, such as color.background.selected, where appropriate.Typography: Check heading hierarchy and readability, especially where your app sets its own font weights.Search and accessibility: Review custom search inputs and check selection visibility, keyboard focus and readability in both light and dark themes.Refer to the Atlassian Design System documentation for component and token guidance.

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