Updates

An update repeats the same steps as an install: the example pages are refreshed and your existing data is brought up to date.

Almost none of that is visible. The one thing users see is a banner.


#What you see

An update repeats the install steps: example pages refreshed, existing data brought up to date. The only signal users see is an in-app "Addon is outdated" banner with an "Update now" link for admins, which appears once a newer version has been out for more than two days.

Atlassian's Connected apps page on the Installed apps tab, listing Approval, Capable for Confluence All-in-One, Diagrams, Explorer, Image Library, Macros, Markdown and Publishing, all by Capable and e
Every Capable app with a newer version carries a label of its own in the site's list of connected apps.

#What needs approval

An update that requests a new permission needs a Confluence administrator to approve it before it applies. Everything else applies without you doing anything.

The Capable for Confluence All-in-One entry in Connected apps, with Update, Unsubscribe and Uninstall buttons in the top right and Details, Connections and Authorisation tabs beneath.
Opening the app itself gives an administrator the button that applies a version which is waiting on them.

#A few things worth knowing

  • Data migrations run as part of an update. They are not visible and do not need a maintenance window.

  • The example pages are refreshed on update, so local edits to them will not survive.

  • If the outdated banner persists after updating, a hard reload usually clears a stale cached bundle.



Mostly invisible. Approve the permission changes.