pyaniz/Thursday
Watch
1
1
Fork
You've already forked Thursday
 0
Code Issues 30 Pull requests Projects Releases Packages 1 Wiki Activity Actions

Fix: expansions inherit tags, search looks through them; versioning is now 0.x (0.140.14) #102

Merged
pyaniz merged 2 commits from staging into main 2026-10-26 18:59:22 -05:00
Conversation 0 Commits 2 Files changed 30 +666 -128
claude-code commented 2026-10-26 16:11:52 -05:00
Collaborator

0.140.14: expansions inherit tags, search looks through them (and the versioning change)

Versioning: the project is beta, so the major number is 0 and the old major moved into the minor. 1.40.13 is now 0.140.13, and every earlier 1.A.B is 0.1A.B. VERSION and the release notes are relabelled accordingly.

  • Expansions always inherit every tag of their base game (union when several); the base game is never changed by what is done on an expansion.
  • Expansions can have their own tags: add a tag, or remove an inherited one (like permissions flowing down from a folder). Same one-vote rule; migration V63 adds game_tags.mode.
  • Search sees expansions from the base game's side (Collection name search and tag filter, and the roulette): a base game comes back when only an expansion matches, labelled via (roulette: "Solo (with Forgotten Circles)"). Expansions are never returned on their own.
  • Docs updated: Community tags, Collection and Game roulette help pages, docs/features/GameRoulette.md.

Tested: unit tests for the inheritance rules (test_tag_inheritance.py) and the roulette engine; the Collection search logic checked in a script; npm run build. Not tested: migration V63 and the tag endpoints against a real database, the expansion tag screen and the "via" labels visually.

🤖 Generated with Claude Code

## 0.140.14: expansions inherit tags, search looks through them (and the versioning change) **Versioning:** the project is beta, so the major number is 0 and the old major moved into the minor. 1.40.13 is now **0.140.13**, and every earlier `1.A.B` is `0.1A.B`. `VERSION` and the release notes are relabelled accordingly. - Expansions **always inherit every tag of their base game** (union when several); the base game is never changed by what is done on an expansion. - Expansions can have their **own tags**: add a tag, or remove an inherited one (like permissions flowing down from a folder). Same one-vote rule; migration V63 adds `game_tags.mode`. - **Search sees expansions from the base game's side** (Collection name search and tag filter, and the roulette): a base game comes back when only an expansion matches, labelled **via <expansion>** (roulette: "Solo (with Forgotten Circles)"). Expansions are never returned on their own. - Docs updated: Community tags, Collection and Game roulette help pages, `docs/features/GameRoulette.md`. Tested: unit tests for the inheritance rules (`test_tag_inheritance.py`) and the roulette engine; the Collection search logic checked in a script; `npm run build`. **Not tested**: migration V63 and the tag endpoints against a real database, the expansion tag screen and the "via" labels visually. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Fix: expansions inherit tags, can add and remove their own, and search looks through them; versioning is now 0.x (0.140.14)
All checks were successful
Build and Publish Containers / build-and-push (push) Successful in 44s
Details
Mirror to GitHub / mirror (push) Successful in 22s
Details
a9bcd82449 
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Fix: global admin variables now sync on startup, with Telegram handle and Discord support (0.140.15)
All checks were successful
Build and Publish Containers / build-and-push (push) Successful in 43s
Details
Mirror to GitHub / mirror (push) Successful in 20s
Details
91b15b97d7 
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
pyaniz merged commit f3bc05d832 into main 2026-10-26 18:59:22 -05:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
audit

   
bug
Something is not working

  
cleanup

   
docs

   
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
new feature
This feature doesn't exist and needs to be created

  
P0

   
P1

   
P2

   
P3

   
question
More information is needed

  
roadmap
Tasks from the official roadmap

  
security

   
wontfix
This won't be fixed

No labels
audit
bug
cleanup
docs
duplicate
enhancement
help wanted
invalid
new feature
P0
P1
P2
P3
question
roadmap
security
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pyaniz/Thursday!102
No description provided.