# Track recent changes

Copy as Markdown[View as Markdown](/docs/development/guides/last-updated-dates.md)

***

**Added in** `eventcatalog@5.12.0`

EventCatalog can show when each part of your catalog last changed. The dates come from your git history, so people can see whether a page is current or has drifted, and nobody has to update a date by hand.

Use this when you want to answer questions like:

* Is this documentation still up to date?
* When did this schema or OpenAPI file last change?
* What changed in the catalog recently?

![EventCatalog homepage with the Recently updated list beside the architecture graph, showing domains and services and when each one last changed](/assets/images/homepage-recently-updated-03f0795a87c7cfec191fdee7e6a62a89.png)

## Turn on last updated dates[​](#turn-on-last-updated-dates "Direct link to Turn on last updated dates")

Last updated dates are off by default. Turn them on with `lastUpdated.enabled` in your `eventcatalog.config.js` file.

eventcatalog.config.js

```
module.exports = {
  lastUpdated: {
    enabled: true,
  },
};
```

The dates are read from git once per build.

## Where dates are shown[​](#where-dates-are-shown "Direct link to Where dates are shown")

### Resource pages[​](#resource-pages "Direct link to Resource pages")

Each resource page (domains, systems, services, messages, agents, flows and so on) ends with **Last updated on 10 Nov 2026**.

The date is the newest commit to any of the resource's own files:

* its `index.mdx` page
* its schema (`schemaPath`, or the local files in a message's `schemas` list, including `file://` refs)
* its specifications (OpenAPI, AsyncAPI, GraphQL and generic files listed in `specifications`)
* its `changelog.mdx`

Other files in the resource's folder are not counted. For example, a domain folder holds its services, and a change to one of those services does not change the domain's date.

The date sits in the page footer, next to the **Edit this page** link when you have set [`editUrl`](/docs/api/config.md#editUrl).

### Specification pages and the schema explorer[​](#specification-pages-and-the-schema-explorer "Direct link to Specification pages and the schema explorer")

OpenAPI, AsyncAPI, GraphQL and generic specification pages show when that specification file last changed.

The [Schema Explorer](/docs/development/guides/resources/schemas/explore-schemas/schema-explorer.md) shows a date for each schema and specification. For a schema that comes from a schema registry, EventCatalog uses the date the registry reports.

### Homepage[​](#homepage "Direct link to Homepage")

The homepage shows a **Recently updated** list. Resources, message schemas and specifications each get their own row, so you can see a schema change even when the message page did not change.

When the [architecture graph](/docs/development/guides/architecture-graph.md) is on, the list sits beside it on wide screens (as in the screenshot above). Each row shows the resource type and version, and how long ago it changed. Hover over the time to see the full date.

Change from earlier versions

Before 5.12.0, the homepage showed the recently updated list whenever the architecture graph was turned off. The list now needs `lastUpdated.enabled`.

## When no date is shown[​](#when-no-date-is-shown "Direct link to When no date is shown")

EventCatalog shows no date rather than a wrong one. Dates are left out when:

* git is not installed where the catalog is built
* the catalog is not in a git repository
* the repository is a **shallow clone**
* the file has not been committed yet

When this happens, the build prints one warning that says why, for example:

```
[EventCatalog] lastUpdated is on, but the catalog is not in a git repository. Pages show no last updated date.
```

### Build from a full clone[​](#build-from-a-full-clone "Direct link to Build from a full clone")

In a shallow clone, the oldest commit lists every file as added. Every page would look like it changed on that day, so EventCatalog does not show dates.

Many CI systems and hosting platforms clone shallow by default. Build from a full clone instead:

**GitHub Actions**: set `fetch-depth: 0` on `actions/checkout`.

.github/workflows/build.yml

```
- uses: actions/checkout@v4
  with:
    fetch-depth: 0
```

**Vercel**: set the environment variable `VERCEL_DEEP_CLONE=true`.

**Docker**: if you build the catalog inside a Docker image, the build stage needs git installed and the repository's `.git` folder (check it is not in your `.dockerignore`).

## Related[​](#related "Direct link to Related")

* [`lastUpdated` configuration reference](/docs/api/config.md#lastUpdated)
* [Changelogs](/docs/development/guides/changelogs/introduction.md)
* [RSS feeds](/docs/api/config.md#rss)