Skip to content

v0.28.11 - Documentation overhaul (2026-03-22)

What Changed?

This release focuses on documentation quality improvements across the entire project. Typos in the pilotlamp GAS test scripts were fixed, and task command names in Taskfile were updated to align with the current naming conventions (env:setup, clasp:push, clasp:version).

What's New

Main Feature: Documentation overhaul

What it does: Rewrites and updates all developer documentation under docs/dev/ and docs/getting-started/ to reflect the current codebase, task commands, and module structure.

Changes include:

  • Removed all emoji markers from documentation files
  • Updated all task command references to current names (e.g., task env:setup, task deploy:gas -- X.Y.Z)
  • Unified docs/getting-started/ directory (removed legacy docs/getting_started/ with underscores)
  • Updated module listings to reflect the 7-module architecture
  • Fixed API references in GAS test scripts (pilotlamp/)
  • Rewrote docs/dev/contents.md with table format and updated class diagram

Added

  • Nothing new added.

Changed

  • docs/dev/: Rewrote build.md, bundle.md, setup.md, install.md, formatter.md, linter.md, testing.md, push.md, docs.md, contents.md, contributing.md, conventions.md, gitlab.md, styleguides.md
  • docs/getting-started/: Updated README.md, installation.md, first-steps.md, practical-workflows.md
  • docs/index.md: Updated feature list to reflect 7-module architecture
  • CLAUDE.md: Removed redundant sections; updated task command syntax
  • README.md: Updated version and task command references
  • Taskfile: Renamed setup tasks to env:setup namespace; renamed bump:gas tasks to deploy:gas

Fixed

  • pilotlamp/main.js: testColsoleLog → testConsoleLog
  • pilotlamp/testDataMap.js: "testIsDataMap" → "testIsDataFrame" (copy-paste bug)
  • pilotlamp/testPivotTable.js: "noEmptyClls" → "noEmptyCells"
  • pilotlamp/jestDataFrame.js: "should throw undefined" → "should return undefined"

Is It Safe to Upgrade?

  • Breaking Changes: No
  • Backward Compatible: Yes

Documentation and task command renames only. No API changes.

Release Details

  • Date: 2026-03-22
  • Version: v0.28.11
  • gaslamp: 68
  • pilotlamp: 25
  • Files Changed: 30+
  • Commits:
    • 4ed305d fix(pilotlamp): fix typos in test scripts
    • 9c0aedb refactor(taskfile): rename setup tasks to env:setup namespace and split deps
    • 2a857fb refactor(taskfile): rename bump:gas tasks to deploy:gas with CLI_ARGS syntax
    • bd43188 docs: update README and CLAUDE.md for v0.28.10
    • 87f2fc8 docs(index): update features list and remove emojis
    • ba0884d docs(getting-started): update module list and remove emojis
    • dc98423 docs: remove legacy getting_started directory and mkdocs entry
    • de1a806 docs(installation): remove emojis and fix AfterGlow instantiation
    • 6648aa1 docs(first-steps): remove emojis and fix sheet insertion safety
    • e8e87b1 docs(practical-workflows): remove emojis and fix sheet insertion safety
    • 23cc914 docs(gears): remove emojis and fix API references
    • 2d7c191 docs(setup): update tool versions and use uv sync
    • 583aa6e docs(install): use task wt:create/cleanup and add cleanup step
    • b76a833 docs(build): rewrite to focus on compile step only
    • 859d6e4 docs(formatter): fix script name and use task format
    • fb6bd24 docs(linter): fix script name and use task lint
    • 25afd78 docs(testing): remove stale test count and add task test
    • 1fa13a0 docs(bundle): fix iife typo and add task bundle
    • ff08372 docs(push): fix task name and clean up
    • 3f2dfca docs(docs): rewrite and remove stale TypeDoc migration notes
    • a38569a docs(contents): rewrite with current structure and remove stale content
    • 304cb4a docs(dev): update task commands and fix markdown lint warnings
    • ec4dcb5 docs(contributing): update workflow commands and TypeDoc reference
    • 38ba636 docs(dev): update conventions and gitlab workflow docs
    • 3ff672b docs(styleguides): fix Contents link label and Markdown style example

Known Issues

  • None.

Next Steps

  • Continue expanding module documentation under docs/modules/.