RFC: Een nieuwe versiebeheerstrategie voor Discourse

Hi,

I used to use the beta tag and am now trying to update my scripts to use the new setup. Here’s how the repository looks as far as I can tell:

* b541e99ea2 (origin/tests-passed, origin/main, origin/latest) DEV: Exclude new table in IntermediateDB config
* 02dfb651ae DEV: Add support for converting and importing `category_moderation_groups`
.
.
.
* 1dde082e96 UX: update lightbox quote icon to apply shadow (#36247)
* 3e7317b334 (tag: v2025.12.0-latest, tag: release) DEV: Begin development of v2025.12.0-latest (#36249)
| * 48167b94d6 (origin/release/2025.11) Backport limited body overflow (#36256)
| * 75d61b40ee (tag: v2025.11.0) DEV: Bump version on `release/2025.11` to `v2025.11.0` (#36251)
|/  
* e3f0320395 FIX: uses overflow hidden body on iOS (#36248)
.
.
.
* 05cd20d401 Bump version to v3.6.0.beta3-latest
* 8a3cb59d5b (tag: v3.6.0.beta2, tag: latest-release, tag: beta) Bump version to v3.6.0.beta2
* 21e5ded097 DEV: remove redundant data attr when cooking posts (#35650)
  • Is it expected that the beta tag is still pointing at v3.6.0.beta2?
  • Is it expected that the release tag is not pointing to a revision on the release/2025.11 branch?

Thanks :slight_smile:

2 likes