Repository navigation
Conversation
dlt ships the workspace files, the dependencies and the agent setup, so nothing here can go stale.
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
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.
Overview
dlthub-init no longer ships a workspace of its own. It runs
dlthub initfrom the newest dlt that uv resolves and then installs the dependencies withuv sync. The workspace files, the dependencies and the skills, rules and MCP server of the coding agent all come from dlt, souvx dlthub-init@latestis current as soon as dlt is, without a dlthub-init release.Until now the package bundled a minimal workspace (
pyproject.toml,uv.lock,.dlt/*,.mcp.json,__deployment__.py) and five Claude-only skills copied from the AI harness. An hourly workflow driven from the agent loop kept that bundle in sync with dlt and the harness, and most of the git history is its commits. The bundle had drifted anyway: the skills no longer matched the harnessinittoolkit, and agents other than Claude got nothing.What runs depends on the dlt that uv resolves:
dlthub init --agent. In an existing project it lists the files it changes and the lines it adds and asks before writing;-yaccepts. It sets up the detected or named coding agent.dlthub init, thendlthub ai init. Nothing is merged: existing files are kept, an existing workspace only gets the agent setup, and--overwritemaps to--force.Releasing changes too: there is no
CHANGELOG.mdany more.make prepare-releaseopens a release pull request, and merging it tags the merge commit and creates the GitHub release with generated notes.Changes
Every commit is one changelog entry, so this PR should be merged with a merge commit or rebased, not squashed.
CLI (
feat!: create the workspace with dlthub init instead of bundling one)dlthub init:--name,--overwrite,--skip,--dependencies,--dry-run,--agent NAME,-y. Options of dlthub-init:DIR(created when missing),--no-sync,--no-telemetry,-v.--no-pyproject,--no-gitignoreand--mergeare removed (merging is the default now), as are the uv installer and the two beaupy prompts.--agent.uv syncthen runs behind a spinner and its output is replayed when it fails, followed by the next steps. A faileddlthubstep prints the step, the exit code and a hint, for example to re-run with-yor--skip.--no-telemetry,DLTHUB_INIT_TELEMETRY=0andDO_NOT_TRACK=1also turn dlt's telemetry off in thedlthubcommands it runs, for that run only.dlt>=1.27.2,packagingandrich;beaupyandposthogare gone.Workflows and CI
ci: remove the hourly workflow that refreshed the bundled workspace:bump-dlthub-init.yml, its changelog script andnoop.yml.ci: run on pushes to devel: the push trigger pointed at the stalemain.ci: run the integration tests on older dlt that cannot merge: a newolder-dltjob runs the end-to-end tests with dlt 1.27.2 (the floor) and 1.32.0 (the newest stable) on Ubuntu and Windows. The existing jobs run everything on the locked dlt on Ubuntu, macOS and Windows.Releasing (
ci: release from a labelled pull request with notes generated by github)make prepare-release [LEVEL=minor|major]runs on your machine, from a cleandevelatorigin/devel. It checks that the tag and the release branch don't exist and no release pull request is open, shows the commits since the last tag and asks for confirmation. It then bumps withuv version --bump, commitschore: bump version to X.Y.Zonchore/release-vX.Y.Z, pushes and opens a pull request labelledrelease, which runs CI. It never cleans up, so you stay on the release branch even when a step fails.GITHUB_TOKENwould not start CI anyway.release.yml, which tags the merge commitvX.Y.Zand creates the GitHub release with--generate-notes..github/release.ymlkeeps the release pull requests out of the notes.make publishstill uploads to PyPI by hand.CHANGELOG.md,release-dlthub-init.ymland its changelog script are deleted. The PR template says the title is the line of the release notes.Development
chore: develop and test against dlt 1.33.0a2:[tool.uv] constraint-dependencieslocks the dev environment to the first dlt pre-release that merges. It only affects this repo's lock, not users. Drop it once dlt 1.33.0 is released.chore: remove the make targets that pin a workspace to a local platform stack:workspace-env,workspace-local,workspace-devandscripts/pin_workspace_urls.pywere copied from dlthub-start; dlthub-init never talks to a platform stack.chore: add claude rules for tests, docstrings and heresy:.claude/rulesand the two skills that point at them. A releasing rule comes with the release commit.docs: describe what dlthub-init runs, its options and the supported dlt versions: README and CONTRIBUTING rewritten.Try it with the dlt pre-release
uv never picks a pre-release on its own, so pin dlt with
--with. Without it you get the newest stable dlt (1.32.0) and the two-step path, which is worth trying too.From GitHub, without a checkout:
From a checkout of this branch:
--refreshpicks up commits pushed since your last run.Worth trying:
--agent claude|cursor|codex|cortexand without it from inside an agent session, where the agent is detectedpyproject.tomland a.gitignore. dlthub lists what it changes and asks: answering N changes nothing and exits non-zero,-yapplies the changes,--skipkeeps existing files, and--overwriteoverwrites the dependency file,.gitignoreand.dlt/.workspaceafter asking--dry-run, which prints the plan and writes nothingTests
dlthubcommands for each dlt version and mode, where the global flags and--agentgo, the telemetry environment, the failure hints and theuv syncreplay.dlthub init, the agent setup anduv sync. On dlt 1.33.0a2 they also merge into an existing project with-y; on older dlt they check that existing files are kept. They pass locally on 1.33.0a2, 1.32.0 and 1.27.2.make prepare-releasewas tested against a scratch clone with a local origin and a stubgh, including the failure paths. The GitHub side of releasing (the label andrelease.yml) runs for the first time on the next release.