Skip to content

Commit fdc5b13

Browse files
committed
Bump module.json version 0.0.2 -> 0.1.0
No GitHub releases have ever been cut (git tag is empty), so the "releases/latest" manifest URL has been 404ing and Foundry's update check has never had anything to resolve. This commit prepares the next real release. Why 0.1.0 and not 0.0.3: the player-character ownership work (FM-CH1 + FM-CH2) shipping in the same release feels like a minor feature bump, and 0.1.0 cleanly leaves behind the confused 0.0.x state where the only ever-released version was 0.0.2. The download URL is also updated to v0.1.0 for consistency with the source-of-truth, though the release workflow rewrites this field at tag-push time anyway.
1 parent 93fea42 commit fdc5b13

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

module.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"id": "chronicle-sync",
33
"title": "Chronicle Sync",
44
"description": "Bidirectional sync between Chronicle worldbuilding platform and Foundry VTT. Syncs journals, maps, tokens, drawings, shops, and calendars in real-time.",
5-
"version": "0.0.2",
5+
"version": "0.1.0",
66
"compatibility": {
77
"minimum": "12",
88
"verified": "14",
@@ -16,7 +16,7 @@
1616
],
1717
"url": "https://github.com/keyxmakerx/Chronicle-Foundry-Module",
1818
"manifest": "https://github.com/keyxmakerx/Chronicle-Foundry-Module/releases/latest/download/module.json",
19-
"download": "https://github.com/keyxmakerx/Chronicle-Foundry-Module/releases/download/v0.0.2/chronicle-sync.zip",
19+
"download": "https://github.com/keyxmakerx/Chronicle-Foundry-Module/releases/download/v0.1.0/chronicle-sync.zip",
2020
"license": "MIT",
2121
"esmodules": [
2222
"scripts/module.mjs"

0 commit comments

Comments
 (0)