Releases: dlt-hub/dlthub-init
Releases · dlt-hub/dlthub-init
dlthub-init 0.1.1
Changed
- Refreshed the bundled minimal workspace
uv.lock, bumpingdltto1.28.0along with its transitive dependencies.
Full Changelog: v0.1.0...v0.1.1
dlthub-init 0.1.0
Added
- Initial release:
uvx dlthub-init [dir]scaffolds a dltHub workspace into a new or existing directory and optionally creates the virtual environment. - Non-destructive by default: safe to run in an existing directory. The run stops only if
.dlt/.workspacealready exists (the directory is already a workspace, exit code2); any other existing file is left untouched and reported as skipped.uv.lockis written only alongside a freshly createdpyproject.toml. Flags:--force,--merge,--no-pyproject,--no-gitignore,--no-sync,--yes. - Bundled minimal workspace with loosened dependency ranges and a committed
uv.lockfor reproducible installs. uv syncruns by default behind an interactive confirmation; a failed sync degrades to a warning so the scaffold still succeeds.make generate-skills/update-skills/check-skillspopulate the rootskills/directory from the dltHub AI workbench'sinittoolkit, pinned to aWORKBENCH_REFcommit (with a CI drift guard), mirroringdlthub-start's AI-generation flow.- Scaffolded workspaces receive the bundled skills: copied into
.agents/skills/(the canonical location most agents read) and linked into.claude/skills/via relative symlinks (copied on Windows or when symlinks are unavailable). The skills ship in the wheel from the single-sourceskills/directory. - After scaffolding, the next steps point you to open your coding agent in the workspace (the
cdanduv syncsteps drop out when not needed).