From f8657bc1db26eb7c4007510cdfc73e13952c6682 Mon Sep 17 00:00:00 2001 From: Vyncint Ng <115854244+vyncint@users.noreply.github.com> Date: Sun, 6 Sep 2026 13:37:14 +0700 Subject: [PATCH] chore: track with mossaic action v0.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The pin was `@v0.6.0` while `version:` is left on `latest`, so this repository was already running **mossaic-art 0.7.0** from crates.io through the **0.6.0 action wrapper** — and the two fixes that matter here live in `action.yml`, not in the tool: - **The midnight split.** The 0.6.0 wrapper runs the tracker twice, `--format json` then `--format markdown`, and each run makes its own GraphQL query and its own `Local::now()`. Across a local midnight the two halves land on different days: the gate reads `today-short` from the first call and the issue comment carries the body of the second. This repository splits them by design — track.yml gates on `steps.art.outputs.today-short` and posts `steps.art.outputs.markdown` — and its cron is 23:30 local, with a `cargo install` ahead of it, so a delayed run lands on the boundary. The 0.7.0 wrapper pins the markdown call to the date the json call reported. - **The empty subject.** `fail-on: holed` interpolated the `text:` input, which is empty by construction for a `matrix:` plan like this one, so the annotation read " can no longer be drawn cleanly this year". `fail-on` is `never` here today, but it is one line from not being. Verified against this repository's own `heart.art` and plan inputs before bumping: the json parses, `start_week` is 35 and `columns` is 11, and the posted markdown now carries `### Heart · 2026 · week 35, 11 columns` — the placement guard README.md describes and no report line used to carry. The holed sentence also reads as a sentence again ("14 days inside the letters are already lit, and nothing takes them away"); 0.6.3 had moved the verb so it described the letters rather than the days. The `("0.5.0")` example in the `version:` comment goes to `("0.7.0")` in the same pass — it was illustrating a pin two releases behind the one in use. Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com> --- .github/workflows/track.yml | 4 ++-- README.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/track.yml b/.github/workflows/track.yml index b91beb4..f222341 100644 --- a/.github/workflows/track.yml +++ b/.github/workflows/track.yml @@ -43,7 +43,7 @@ jobs: persist-credentials: false - id: art - uses: vyncint/mossaic/action@v0.6.0 + uses: vyncint/mossaic/action@v0.7.0 with: # The picture, seven rows by thirteen columns. `matrix` rather than # `text` because a heart is not a letter: it uses the whole week, @@ -72,7 +72,7 @@ jobs: # the failure notification you already get does the reminding. fail-on: never # Which mossaic release does the tracking. The default, latest, - # follows crates.io; pin a number ("0.5.0") to freeze it. Left on + # follows crates.io; pin a number ("0.7.0") to freeze it. Left on # latest deliberately: this repository is where a mossaic release # gets exercised against a real contribution graph, so following # the newest published version is the point of it. diff --git a/README.md b/README.md index f4b99d1..2f7d477 100644 --- a/README.md +++ b/README.md @@ -76,7 +76,7 @@ Exactly the four steps in [mossaic's action guide][guide]: 4. Run once by hand from the Actions tab (with optional `auto_commit` checkbox), rather than waiting for tomorrow. -The action is pinned to `vyncint/mossaic/action@v0.6.0`, not `@main`, so it +The action is pinned to `vyncint/mossaic/action@v0.7.0`, not `@main`, so it changes when I say so. `matrix:` arrived in 0.6.0. ## Two things GitHub does that will bite you