Skip to content

Commit

Permalink
Add v5.2, v6.0, and v6.1 tags to README
Browse files Browse the repository at this point in the history
  • Loading branch information
laymonage authored and gasman committed Sep 26, 2024
1 parent 0e71443 commit d72c386
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -229,6 +229,14 @@ By default, `django-csp` is not enabled since Wagtail isn't fully compatible yet

The `main` branch of this demo is designed to work with both the latest stable release and the latest `main` branch (development version) of Wagtail. To run the demo against a specific version of Wagtail, we have created [git tags](https:/wagtail/bakerydemo/tags) for the latest commits that work with each feature release.

- [`v6.1`](https:/wagtail/bakerydemo/releases/tag/v6.1)
- [`v6.0`](https:/wagtail/bakerydemo/releases/tag/v6.0)
- [`v5.2`](https:/wagtail/bakerydemo/releases/tag/v5.2)

<details>

<summary>Older tags</summary>

- [`v5.1`](https:/wagtail/bakerydemo/releases/tag/v5.1)
- [`v5.0`](https:/wagtail/bakerydemo/releases/tag/v5.0)
- [`v4.2`](https:/wagtail/bakerydemo/releases/tag/v4.2)
Expand All @@ -237,6 +245,8 @@ The `main` branch of this demo is designed to work with both the latest stable r
- [`v3.0`](https:/wagtail/bakerydemo/releases/tag/v3.0)
- [`v2.16`](https:/wagtail/bakerydemo/releases/tag/v2.16)

</details>

The tags point to the last commit just before the requirements were updated to the next Wagtail version. For example, the `v4.2` tag points to the commit just before the bakerydemo was updated to use Wagtail 5.0. This ensures that the tagged demo code contains the latest updates possible for the supported version.

There were no updates to the demo between Wagtail 4.1 and 4.2, so the `v4.1` and `v4.2` tags point to the same commit.
Expand Down

0 comments on commit d72c386

Please sign in to comment.