Changelog

Latest release changes

GoLazy v0.1.12 adds asset upload support for object-storage deployments, S3-compatible storage, local package documentation models, app-versioned CLI handoff, and optional tmux development workspaces. Existing v0.1.11 applications can upgrade incrementally.

Framework

• lazyassets.Registry.Upload writes registered assets to any lazystorage.Writer. The default mode uploads content-hashed permanent paths plus manifest.json, which fits CDN and static ingress deployments. Read Deployment Checklist.
• lazyassets.WithBaseURL makes asset helpers and importmap fragments emit absolute asset URLs while keeping registered asset paths and routing path-based.
• golazy.dev/lazystorage/s3 provides an S3-compatible storage backend with signed read/write/list/delete operations, public URL generation, bucket creation, and polling watches. Read Mailers And Storage.
• golazy.dev/lazydoc shares package documentation loading, extraction, JSON, and search models between the website and lazy docs.
• In lazydev builds, lazyapp now reads the local view root from GOLAZY_VIEW_PATH. Production builds continue to use the application's configured embedded views.
• The public golazy.dev/lazyviews package was removed. The lazy CLI owns development view-path resolution.

CLI and generated apps

• App-bound lazy commands now run with the CLI version matching the app's golazy.dev requirement in go.mod, installing the matching CLI into the user cache when it is missing. Read Run With lazy.
• lazy --skip-version-check keeps the directly invoked binary in control for intentional local CLI tests against apps that require another framework version.
• Apps can opt into a tmux development workspace with lazy.toml. The default lazy command opens service panes, runner panes, the app development loop, and lazy command-center through mise. Read Run With lazy.
• lazy docs inspects local package documentation and prints package summaries, search results, or JSON.
• lazy --version now reports v0.1.12, so lazy new selects the matching sample application template once the coordinated release is published.
• The generated sample app keeps business services in top-level services/, outside the web-facing app/ tree. Read Application Structure and Services And Context.

Website and guides

• The install guide documents the public install.sh flow, including the installer's mise setup path and app-versioned CLI behavior.
• The new Development guide collects the local mise setup, application and development-service conventions, JavaScript and Tailwind asset pipelines, and the lazy command workflow.

Read the Upgrade Guide before moving an existing application forward.