Verifying a release yourself
This page is for reporters, editors and fact-checkers who want to confirm a release with their own eyes instead of trusting a post, a press release or this help. Everything here works without an account and without installing Exponential. You need a browser, and for the second method a computer with Git.
Contents
- Method 1: in a browser
- Method 2: with Git
- Method 3: on Packagist
- Confirming what a release contains
- When the results disagree
Method 1: in a browser
- Open github.com/se7enxweb/exponential/releases.
- Find the version. Each release shows its tag (for example
v6.0.14) and the date GitHub published it. - Open the tag's page from the release overview, which lists a "Release url" for each
6.0.x version, for example
https://github.com/se7enxweb/exponential/releases/tag/v6.0.14.
Do not rely on the order of the list alone: confirm the newest version by its number with method 2.
Method 2: with Git
The repository's own documentation gives these commands (Getting the code). Without cloning:
git ls-remote --tags https://github.com/se7enxweb/exponential.git 'v6*'Inside a clone:
git clone https://github.com/se7enxweb/exponential.git
cd exponential
git fetch --tags
git tag -l 'v*' --sort=version:refname | tail -5Expected on 18 October 2026, the five newest tags, newest last:
v6.0.10
v6.0.11
v6.0.12
v6.0.13
v6.0.14The date of a tag's commit:
git log -1 --format='%ad' v6.0.14Always sort with --sort=version:refname; a sort by name puts v6.0.10 before v6.0.8
(How version numbers work).
Method 3: on Packagist
The kernel is the Composer package se7enxweb/exponential. Its page lists every version Composer can install. Velocity is se7enxweb/exponential-velocity. A version appears there after Packagist has read the tag; the extensions guide notes that if a new version does not appear, the repository's webhook to Packagist may be missing (Extensions guide).
Confirming what a release contains
| Question | How to check |
|---|---|
| Is feature X in version Y? | Search the changelog of Y (Reading a changelog), then the ledger, whose "Release" column names "the release tag that first contained the change" (history) |
| Is a commit in a release? | git tag --contains <hash> in a clone lists every tag that includes it |
| What changed between two releases? | git log --oneline v6.0.13..v6.0.14 |
| Which version does a site run? | Only its owner knows for sure; do not guess from screenshots |
When the results disagree
| Disagreement | Likely reason | What to print |
|---|---|---|
| Tag date and GitHub release date differ | The release was published later than the tag; the release overview lists both, for example 6.0.13: tag 18 April 2026, release 20 April 2026 | The tag date, and say so (Verifying dates) |
| Packagist does not show a tag that GitHub shows | Packagist has not read it yet | Wait, or say "tagged on GitHub" |
| Your clone does not show a tag | You have not fetched it | Run git fetch --tags |
| A blog says a version exists that you cannot find | It may be work on the main branch or an error | Do not print it (Covering the 6.0.15 line) |
Related pages
- Published versions never change
- Verifying dates
- Fact-checking guide
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.