apiPulse.app

Atlassian

Atlassian developer platform changelog updates

Atlassian API Changelog Monitoring

Atlassian ecosystem changes can affect marketplace apps, Jira and Confluence integrations, and admin workflows used across enterprise teams. This Atlassian API Changelog Monitoring page helps you review updates in a structured way before they ripple into production usage.

Better Atlassian API Changelog Monitoring helps marketplace and internal-tool teams understand changes to platform behavior, APIs, and policies before customers raise issues. It supports a cleaner release process by turning changelog review into a routine instead of a scramble.

The benefit of Atlassian API Changelog Monitoring is simple: your team gets a repeatable way to watch changes, evaluate risk, and act before small upstream updates turn into customer-facing bugs. Atlassian developer platform changelog updates

Atlassian API down?

Atlassian API down? Soon we will add direct API status monitoring alongside Atlassian API Changelog Monitoring. For now, go to the official API status page on the Atlassian website. In the future, we plan to detect downtime signals even before the public status page is updated.

Recent changes

Showing the last 10 changes from this feed.

06-01-2026

[Added] Forge LLM is now in Preview and available as a billable capability

Forge LLM is now officially in Preview. This transition makes Forge LLM available to all developers as a billable capability.What’s changingProgressive Rollout: We are using a progressive rollout strategy to enable Preview access. This means it may take a few days for the necessary feature flags to reach all tenants.Temporary Error Messages: During this rollout period, you may still see an error message stating: Forge LLM feature is available exclusively in the Development environment through the EAP program. This message will persist until the rollout is complete for your specific environment.Billing: All Forge LLM usage is now billable. Please ensure your apps are associated with a developer space that has active billing details.Model Deprecations: The following older model versions are now deprecated and are not included in the Preview release:claude-sonnet-4-20250514claude-opus-4-1-20250805claude-opus-4-5-20251101What you need to doReview the Forge LLMs pricing to understand how credits and billing work.Update your app configurations to use supported model versions.Verify your billing details in the developer console to ensure uninterrupted service.For technical implementation details, refer to the Forge LLMs API reference.

Source
06-01-2026

[Announcement] Forge embedded macros are now generally available

Forge embedded macros have reached general availability (GA). This feature allows Forge bodied macro apps to render other embedded Forge macro apps, enabling more complex and integrated content experiences within Confluence.What’s changing You can now use the following methods to render embedded Forge macro apps within a bodied macro:UI Kit: Use the AdfRenderer component.Custom UI: Use the view.createAdfRendererIframeProps method from the @forge/bridge package.What you need to do To start using embedded macros in your bodied macro apps:Ensure you are using the latest version of @forge/bridge for Custom UI apps.Implement the AdfRenderer (UI Kit) or createAdfRendererIframeProps (Custom UI) in your macro's rendering logic.Refer to the updated Forge rich-text bodied macros documentation for implementation details and examples.

Source
06-01-2026

[Added] Multi-entry resource bundles for Forge apps now in preview

We're releasing multi-entry resource bundles for Forge apps into preview. This update allows you to group multiple named entry points within a single resource, helping you optimise app performance and stay within resource limits.What's changing Previously, apps with multiple modules required a separate top-level resource entry in manifest.yml for each view, consuming one bundle slot per module. You can now define multiple named entry points within a single resource using the new entry property.You can reference each entry from any module using slash syntax: resource: <resource-key>/<entry-key>. This feature is available for both UI Kit and Custom UI apps.Why this mattersLower bundle count usage: Multiple entries within one resource count as a single resource against the 50-resource limit.Smaller deploy size and faster load times: For UI Kit, the Forge CLI automatically extracts shared dependencies into common chunks. For Custom UI, you can achieve similar benefits by configuring code splitting in your build pipeline (e.g., via webpack or vite).Fully backwards-compatible: Existing apps require no changes. The entry property is optional, and resources without it behave as before.Key detailsMaximum of 50 entries per resource.Entry values must be flat filenames directly within the path directory; nested paths (e.g., views/global.jsx) are not supported.As a Preview feature, this is considered stable but remains under active development and may have shorter deprecation windows.What you need to do To get started, review the updated resources manifest reference for documentation and examples.

Source
05-29-2026

[Deprecation Notice] Brownout Notice: App password deprecation for Bitbucket Cloud

Bitbucket Cloud is transitioning to API tokens to enhance security. As part of this transition, app passwords will be fully deprecated on 28 Jul 2026. To help you identify and migrate any remaining usage before the final removal, we are running a series of controlled brownouts starting 09 Jun 2026. What’s changing:During each brownout window, API requests authenticated using app passwords will fail with an HTTP 401 while Git-over-HTTPS operations authenticated using app passwords will fail with an HTTP 410.What you need to do: You must migrate to API tokens before 28 Jul 2026. API tokens offer improved security, expiration controls, and centralized management. To create and use an API token:Select your Profile icon, then select Account settings. Select Security, then Create and manage API tokens, and then select Create API token.Select Create API token with scopes.Name the token, set an expiry date, select Bitbucket as the app.Assign the necessary scopes and save the token.Update your integration credentials, CI/CD pipelines, and local Git configurations with the new API token.For detailed guidance, see the API token documentation.

Source
05-28-2026

[Announcement] Raising the bar on Marketplace security: Updated cloud app SLOs and new enforcement policy

As recently announced in Raising the bar on Marketplace cloud app security: together we are updating the Marketplace Security Bug Fix Policy to shorten vulnerability remediation timelines for Marketplace cloud apps. These changes ensure a higher security standard across our ecosystem.What’s changing The remediation Service Level Objectives (SLOs) for Marketplace cloud apps are being shortened. The timelines for Data Center apps remain unchanged.Updated Cloud App SLOs (Enforceable September 1, 2026):Critical: 10 daysHigh: 4 weeksMedium: 12 weeksLow: 25 weeksData Center App SLOs (Unchanged):Critical: 12 weeksHigh: 12 weeksMedium: 12 weeksLow: 25 weeksAdditionally, we have published the Marketplace Security Enforcement Policy, a consolidated source of truth for marketplace security compliance expectations, including vulnerability management, OAuth compliance, partner verification, bug bounty participation, and incident response.What you need to doReview the new timelines: Ensure your internal processes are updated to meet the new cloud app SLOs by September 1, 2026.Check your tickets: We have corrected an issue where some AMS Data Center tickets incorrectly showed cloud remediation dates. If you believe a ticket still has an incorrect date, please raise an ECOHELP ticket.Watch the policy page: The Marketplace Security Enforcement Policy is a living document, we recommend "watching" the page for future updates.

Source
05-27-2026

[Added] New hideFlag(id) API available in @atlaskit/flag for programmatic dismissal

The useFlags() hook returned from FlagsProvider (in @atlaskit/flag) now exposes a new hideFlag(id) method on its API, allowing consumers to dismiss a previously shown flag by its id at any time — without needing to retain the DismissFn originally returned by showFlag().This unlocks programmatic dismissal of flags from side-effects such as route changes, network responses, or parent unmounts, where holding onto the original DismissFn is impractical.Migration: This is a backwards-compatible addition. Existing code using the DismissFn returned by showFlag() continues to work unchanged.See the @atlaskit/flag examples on atlassian.design for usage.

Source
05-26-2026

[Removed] New `headingLevel` prop for section message

The new headingLevel prop for @atlaskit/section-message will allow for a more accessible heading structure when using the title prop. See the W3C headings page for more information on how to nest headings correctly.

Source
05-26-2026

[Announcement] Upcoming changes to JQL search functions and issue history

We are adjusting how some JQL features behave to keep search fast and reliable. Queries using functions membersof() and aqlFunction() that expand to very large sets will return an error identifying the clause to adjust. For comments, worklogs, and issue history (searches using operators WAS or CHANGED), JQL searches cover only the most recent entries per issue. Jira data and permissions are unchanged.Effective date: 18 Aug 2026

Source
05-26-2026

[Announcement] Customer messaging for Connect EOS is rolling out for non-public apps and coming to Developer Canary tenants for public apps soon

As Connect approaches end of support in December 2026, we are starting to roll out customer messaging in the admin experience to inform admins when an installed app runs on a soon to be unsupported platform, Connect. Following on from our previous announcement, this messaging will gradually rollout over the next week to be live in production for non-public apps only and is scoped to the admin experience, end users will not see any notices at this stage.On 02 Jun 2026, we will enable customer messaging on Developer Canary tenants for public apps. This will include notices in admin facing experiences so enrolled partners can preview the exact messaging their customers will see and have the chance to adopt the new connectToForgeMigration module in their manifest before it goes live in production.

Source
05-26-2026

[Announcement] New rate limits for Forge Realtime

We are introducing rate limits for Forge Realtime to ensure the stability and reliability of the service for all apps.What’s changing Starting June 26, 2026, a rate limit of 50 requests per app installation per second will be enforced for Forge Realtime. For more information, see our rate limit documentation.Based on our current telemetry, no existing Forge apps exceed this limit, so we do not expect any immediate impact on your app's performance. This change is a proactive measure to maintain service health.What you need to doReview your app's use of the Realtime Events API and Bridge API Realtime method to ensure your request frequency remains within the new limit.If you anticipate needing a higher rate limit for a specific use case, please reach out via the developer support portal.

Source