> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-installation-activation/support-and-maintenance/viewing-revisions.md).

# Viewing Enhancements and Changes to the Software

How to view software enhancements and change history through the ENERCALC SEL release notes page.

A comprehensive list of software revisions is available at [enercalc.releasenotes.io](https://enercalc.releasenotes.io/).

You can also access this page directly from within the software by navigating to: **Help > Enhancement/Change History**

![](https://3887844556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F69DEk6rAGnwtJoSDtHQD%2Fuploads%2Fgit-blob-58604265ab488d782c6e6dd73eb1b10a9a39a0d0%2Frelease-notes.png?alt=media)

To view revisions specific to a particular module or feature, use the tags on the left-hand side of the release notes page.

To return to the main release notes page, click the **ENERCALC** logo at the top of the screen.

You can subscribe to stay informed about future updates via email by clicking the "Subscribe" button at the top of the release notes page. Alternatively, you can visit the subscription page directly here: <https://enercalc.releasenotes.io/subscribe>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enercalc.com/docs/sel-installation-activation/support-and-maintenance/viewing-revisions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.