Point the cask at 1.1.1 and refresh the offline demo - #2
Merged
Conversation
The cask still pinned 1.1.0 and its checksum, so `brew install --cask tokenflow` kept handing out the build with all five defects in it. Version and sha256 now name the v1.1.1 release. The checksum was not copied from the published .sha256 file and trusted: the DMG was downloaded, hashed locally, and the two compared — brew verifies this hash, so a wrong one fails the install outright. The demo page advertised 1.1.0 in its embedded bundle, and its dataHome carried the absolute path of the machine that generated it — including the username — on a page served publicly from GitHub Pages. Regenerated from a throwaway store under /tmp, so the published bundle names no home directory. Same shape as before (60 days, ~1.8k synthetic records, 1.5 MB) rather than the current 160-day default, which would have doubled the page weight for a cosmetic fix. Still flagged "demo": true, still labelled DEMO DATA in the UI, and rendered to confirm it before publishing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Post-release housekeeping for v1.1.1.
Cask
It still pinned
1.1.0and that build's checksum, sobrew install --cask tokenflowkept handing out the build with all five defects in it.The hash was not copied from the published
.sha256and trusted. The DMG was downloaded, hashed locally, and the two compared — brew verifies this value, so a wrong one fails the install outright rather than quietly installing something else:.sha256asset60fd7f5c…837c60fd7f5c…837cAlso confirmed the release URL resolves (HTTP 200) and the DMG contains an app bundle reporting
1.1.1.Offline demo
site/demo/index.htmladvertised"appVersion":"1.1.0"in its embedded bundle. ItsdataHomealso carried the absolute path of the machine that generated it — including the username — on a page served publicly from GitHub Pages. Regenerated from a throwaway store under/tmp, so the published bundle names no home directory.Kept to the original shape rather than today's defaults:
dataHome/Users/<user>/tokenflow-demo-store/tmp/tokenflow-demo-storeThe current 160-day default would have produced 4,582 records and 3.2 MB — double the page weight for a cosmetic fix, so
--days 60matches what was there.Still
"demo": true, still labelled DEMO DATA in the UI, scanned for real identifiers (zero hits), and rendered in a browser to confirm it before publishing.🤖 Generated with Claude Code