Repository navigation
Releases
Releases · Dimagious/garmidian
1.1.2
Fixed
- The community scorecard of 1.1.1 lists 22 warnings in the e2e helpers (
e2e/fixtures.ts,e2e/demo-garmin.ts,e2e/live-key.ts): the scanner lints every file atsconfig.jsoncovers, ande2e/tsconfig.json(added in 1.1.1 fornpm run typecheck) made it cover them. That config is nowtsconfig.e2e.jsonin the root, with the same options, andnpm run typecheckcheckse2e/through it. The scanner finds only files namedtsconfig.json, so it skipse2e/again, as it did up to 1.1.0. The warnings were Obsidian runtime rules (window.setTimeout, noglobalThis, nonode:child_process) that do not apply to Playwright code, which runs in Node, andno-unsafe-*on values read from Obsidian throughevaluate. Nothing inmain.jschanges.
1.1.1
Changed
- The dev kit is obsidian-plugin-dev-kit 0.3.0 (moved with
opdk kit upgrade v0.3.0), so thatopdk scanreports what the community scorecard reports. Four things follow. TypeScript is 6 (typescript^6.0.3, was^5.6.0); the code needed no changes to compile. The ESLint config is renamed fromeslint.config.jstoeslint.config.mjs, because the scanner does not read.mjsfiles and a.jsconfig that imports the kit gets two warnings there;npm run lintlints the same files as before. Thescan.ignorekey is gone fromopdk.config.mjs(the kit removed it: a skipped file was still on the public scorecard), soopdk scannow readssite/too and found 20 CSS warnings in the GitHub Pages stylesheets, which are fixed: the!importantrules on code in the explorer, the block index and the key list now win by specificity, and the reduced-motion rule names the animated elements instead of using*; the "On this page" list is a two-column grid filled top to bottom (each list sets its row count) instead of CSS columns; the unused:has()rule is removed;ui-monospaceis dropped from the code font stack (the next font in it, SF Mono, is the same face) and links lose the 1px underline thickness (the browser default is used, offset unchanged). Screenshots of the home page and all guides before and after, at 1280 and 390 pixels wide, differ by a few single pixels at the ends of link underlines and nowhere else.opdk scannow prints 0 findings and one advisory line forsite/assets/site.js, which no tsconfig covers. - The dev kit is obsidian-plugin-dev-kit 0.2.0 (was 0.1.0), moved with its new
opdk kit upgradecommand: the tag inpackage.json, the lockfile and the two kit workflow lines (ci.yml,release.yml) name commit32a1860. Its lint preset reports a barewindow.<member>again, the check the oldscorecard-check.cjshad; Garmy has none.opdk release checknow also fails when those three places disagree. Typecheck, lint, 499 unit tests, build,opdk scan,opdk release check,readme:check,site:checkand the e2e pass on it. - The sleep and HRV guide says the Choose step groups appear under the Everything kind, and names the Sleep and HRV and recovery kinds.
- The site no longer copies the
phone-*stills, which only feed the directory pictures (tools/listing.mjs). - Build, lint, scanner, end-to-end harness, README films and release are done by obsidian-plugin-dev-kit 0.1.0 (the
opdkcommand, installed from itsv0.1.0tag). Garmy's own settings are inopdk.config.mjs. The scripts it replaces are deleted:assert-bundle.cjs,scorecard-check.cjs,e2e-setup.sh,capture.mjs,version-sync.cjs,make-zip.cjsandassert-versions.cjs. - The release bundle is built by
opdk buildand is now minified:main.jsgoes from 336087 to 285177 bytes (114154 bytes gzipped, was 121404; both measured asgzip -c main.js | wc -con the build oforigin/mainand of this branch). The platform staysbrowser, and the kit also marks@codemirror/stateand@codemirror/viewas external, which Garmy does not import. The kit's bundle check (noprocess,node:imports,__dirname) replacesscripts/assert-bundle.cjs. TheesbuilddevDependency is gone, the kit brings its own. npm run scorecard:checkrunsopdk scan(the scanner's own ESLint configuration foreslint-plugin-obsidianmd0.5.1, plus CSS, source and manifest checks) instead ofscripts/scorecard-check.cjs. The old script's check for a barewindow.<member>(other than timers) insrc/is gone: the kit scanner does not check it yet. The scan reads every tracked file, so the GitHub Pages site (site/, a static web page that never ships inmain.js) is listed underscan.ignore; without that it reports 36 lint and 20 CSS findings insite/assets/, which the old script and the lint config skipped as well.eslint.config.mjsisobsidianPlugin()from the kit, with Garmy's own ignore list, andnpm run lintruns with--max-warnings=0. Theeslint-plugin-obsidianmd(was 0.4.2),typescript-eslintand@eslint/jsdevDependencies are removed: the kit pins its owneslint-plugin-obsidianmdandtypescript-eslint, and@eslint/jsis no longer needed. The@typescript-eslint/no-misused-promisesrule is replaced byobsidianmd/no-misused-promises.- The e2e harness is the kit's
obsidian-plugin-dev-kit/e2emodule:e2e/fixtures.tsis onecreateObsidianTestcall andplaywright.config.tsisdefineObsidianConfig().npm run e2eisnpm run build && playwright test, so the specs run against the minified bundle;npm run e2e:setupandscripts/e2e-setup.share gone. Every test still gets its own Obsidian process, vault copy and user-data folder, now installed, trusted and waited for by the kit instead of fixed sleeps (1500 ms inwin, 800 ms and 1500 ms insync.spec.ts, two of 1500 ms inexisting-notes.spec.ts). The generatede2e-vault.pristine/.obsidian/plugins/folder and its.gitignoreentry are gone: the kit installs Garmy and Dashy into the temp copy. The kit refuses a Garmymain.jsolder thansrc/; the Dashy checkout installed beside it is not checked, so a Dashy build needs no override. - The e2e specs use the kit's helpers:
obsidian.openSettings("garmidian")(the settings spec no longer hunts for a second window),obsidian.waitForMetadataCache(),obsidian.replace()for the fake Garmin (fakeGarmin(obsidian, ...)andinstallDemoGarmin(obsidian, ...)return the fake's handle, and the units spec counts requests withcalls()),obsidian.evaluate()in place of most of theglobalThis as unknown as { app ... }casts (setKeyandopenWizardine2e/fixtures.tskeep theirs),obsidian.runCommand(),obsidian.hideProperties(),obsidian.setTheme(),obsidian.clearNotices(),obsidian.readingView(),obsidian.scrollThrough()andobsidian.mobile()in the capture spec, andonlyWhen("CAPTURE")/onlyWhen("GARMIN_LIVE")in place oftest.skip. Both gates now need the value1, asnpm run capturesets;GARMIN_LIVE=trueno longer runs the live spec. npm run typecheckalso checkse2e/throughe2e/tsconfig.json.- The README films (
film-wizard,film-rebuild,film-languages,film-libraryindocs/screens) are shot with the kit'sdemofixture (a film of stills,film.shot({ hold })) and encoded byopdk demo(settings inopdk.config.mjs).npm run captureisbuild, the capture spec andopdk demo;scripts/capture.mjsis deleted, andnpm run capture -- <word>is gone:npx opdk demo film-libraryre-encodes one film. The frames are 2x on any display (the library poster was 980 x 1000, now 1960 x 2000), the clock is frozen at 2026-11-11, the ribbon, status bar, tab headers and side panels are hidden, a retake replaces the frames instead of appending to the old ones, and a visible cursor shows where the mouse last moved. The GIFs keep 160 colours at 8 fps and their widths; the first frame is still the poster. The stills are retaken in the bullets below. - Releases are cut with
npx opdk release patch(orminor,major, an exactX.Y.Z;--dry-runfirst) in place ofversion-sync.cjsand a hand-pushed tag. It bumpspackage.json,package-lock.json,manifest.jsonandversions.json(an existingversions.jsonentry is never rewritten), moves the CHANGELOG entries under the new version, commits, pushes the annotated tag (tags were lightweight before) and waits forrelease.yml. That workflow is the kit's reusable one, pinned to its full commit: it builds with a read-only token, attestsmain.js,manifest.jsonandstyles.css, and makes a draft whose notes are the CHANGELOG section of the version (the release page showed GitHub's generated list before).opdk releasethen checks the draft against a local build of the tag, publishes it and only then pushes the branch. No zip is built or attached any more (npm run release:zipandmake-zip.cjsare gone), andrelease.ymlruns the unit tests in atestjob before the kit's release jobs.opdk releaseitself runs no tests, so runnpm run release:checkfirst, which now starts withopdk release check(versions,versions.json, manifest rules, CHANGELOG section, build, byte-for-byte reproducibility,minAppVersionagainst the API). Do not release unpushed commits. ci.ymlcalls the kit'splugin-ci.yml(pinned to the same commit) for lint, typecheck, unit tests,opdk scan,opdk release check, the build and thegarmidian-bundleartifact, and keepsreadme:checkas a job of its own. Runners areubuntu-24.04and actions are pinned to commits (they wereubuntu-latestand major tags). The bundle artifact no longer holds a zip.@playwright/testandelectronare pinned to exact versions (1.65.0 and 44.10.2) as the kit documents;jsdomandviteare devDependencies for the unit tests, andobsidian-test-mocksis pinned to 8.0.0 with Dependabot ignoring its major updates.vitest.config.tsisdefineUnitConfig()from the kit: Garmy's own stub for the node tests,obsidian-test-mocksin jsdom for the wizard and settings tests. The coverage gate (90 percent, 80 for branches) now countssrc/app/wizard.tsandsrc/app/settings.tstoo.pages.ymlruns onubuntu-24.04and pins every action to a full commit with its version in a comment (checkoutv7.0.1,setup-nodev7.1.0,configure-pagesv6.0.0,upload-pages-artifactv5.0.0,deploy-pagesv5.0.1; the first two are the commitsci.ymlandrelease.ymlalready use). The checkout no longer keeps the token (persist-credentials: false). The permissions are unchanged:contents: readfor the checkout,pages: writeandid-token: writefor the deploy. Theci.ymlbullet above says runners a...
1.1.0
1.0.1
1.0.0
Full Changelog: https://github.com/Dimagious/garmidian/commits/1.0.0