Skip to content

Releases: udx/dev.kit

Release v0.13.0

27 May 18:56
Immutable release. Only release title and notes can be modified.
7680563

Choose a tag to compare

  • Allow repo-owned manifests to satisfy config contract coverage when they declare explicit config contract metadata or runtime config sections, avoiding forced .env.example files for repos with custom manifest contracts.

Release v0.12.0

27 May 10:20
Immutable release. Only release title and notes can be modified.
1868279

Choose a tag to compare

  • Add generator source refs to .rabbit/context.yaml so generated context points to the dev.kit homepage, source repo, npm package, and installation guide.
  • Validate generated context portability before writing it, rejecting machine-local absolute paths and excluding temporary context files from repo evidence.
  • Add repo-owned context contract and output schema docs to clarify what dev.kit reads, emits, and must not own.
  • Harden guarded command timeouts so child processes are cleaned up by process group without disabling timeout protection.

Release v0.11.0

19 May 19:07
Immutable release. Only release title and notes can be modified.
859bab0

Choose a tag to compare

  • Expose repo-centric workflow status in dev.kit, dev.kit env, and dev.kit repo output so environment checks, context refresh, and gap repair appear as one repo-owned loop
  • Clarify the repo contract boundary between deterministic structured parsing and interpreted prose/session intent
  • Make real-repo validation read-only by default with guarded JSON reports, and move release probe values into repo-owned config

Release v0.10.0

14 May 12:19
Immutable release. Only release title and notes can be modified.
ac46ce4

Choose a tag to compare

  • Remove dev.kit agent so .rabbit/context.yaml is the single generated repo contract
  • Make dev.kit non-destructive at home: inspect env, summarize context status, and guide to dev.kit repo
  • Add generator metadata to .rabbit/context.yaml (tool, repo, version, generated_at)
  • Make dev.kit repo ensure a minimal default repo structure for empty repos: README.md, .github/dependabot.yml, .github/workflows/, .rabbit/, and docs/
  • Add recommended tooling repo output for udx/worker, udx/reusable-workflows, and udx/github-rabbit-action
  • Fix global --json routing so dev.kit --json <command> reaches the requested command instead of falling back to home output
  • Add machine-readable JSON output for dev.kit uninstall --json --yes
  • Ignore exported Copilot session transcripts so local session history does not leak into release diffs
  • Add a repo-owned workflow reference doc for developer and agent best practices tied to dev.kit commands
  • Add a normalized repo-owned AGENTS.md for this repo, sourced from the workflow reference doc
  • Clarify docs for build-default vs runtime env contracts and workflow triggers when releases are created by automation
  • Clarify that scripts and YAML manifests are the execution layer, while docs guide developer and agent decisions
  • Add integration and repo-design docs covering local/remote usage, scope, limits, and how repo contracts fit pipelines

Release v0.9.0

04 May 14:07
Immutable release. Only release title and notes can be modified.
1063c99

Choose a tag to compare

  • Add dev.kit env and env config controls so repo and agent output can reflect actual tool and credential availability
  • Keep .rabbit/context.yaml focused on repo facts, tracing, commands, and gaps instead of inlining engineering practices and canonical workflow text
  • Generate workflow guidance for AGENTS.md directly from the config catalogs and repo context, simplifying the boundary between repo context and agent behavior
  • Rework the docs surface around that model: simplify the README, add focused installation, context, agents, and integration docs, and remove older overlapping overview/workflow/architecture pages
  • Tighten GitHub-first workflow guidance across configs and generated agent instructions
  • Remove dev.kit learn from the public command surface and trim the related configs, templates, and docs
  • Clean up install and packaging flow with global npm postinstall cleanup and explicit npm-versus-curl ownership rules
  • Improve manifest contract tracing with repo-owned evidence from top-level version headers, GitHub references, and actual usage paths
  • Collapse duplicate dependency evidence into single repo entries and avoid false dependency traces from nested YAML metadata or placeholder GitHub refs
  • Add optional tests/real-repos.sh coverage for local public/private repos and trim unused synthetic fixtures
  • Add upgrade-first guidance to generated AGENTS.md and installation/experience docs so new sessions start from the current dev.kit build

Release v0.8.0

17 Apr 18:33
Immutable release. Only release title and notes can be modified.
4b84821

Choose a tag to compare

  • Keep .rabbit/context.yaml focused on repo facts, tracing, commands, and gaps instead of inlining engineering practices and canonical workflow text
  • Generate workflow and practice guidance for AGENTS.md directly from the config catalogs and learning sources, simplifying the boundary between repo context and agent behavior
  • Rework the docs surface around that model: simplify the README, add focused installation, context, agents, and integration docs, and remove older overlapping overview/workflow/architecture pages
  • Tighten GitHub-first workflow guidance across configs, generated agent instructions, and learned templates, including repo-pattern reuse, history-aware debugging, and bot-feedback loops
  • Simplify lesson/template generation by consolidating workflow-tracing signals, deduping reusable templates by template name, and filtering unresolved placeholder template IDs from generated output
  • Clean up install and packaging flow with global npm postinstall cleanup and explicit npm-versus-curl ownership rules

Release v0.6.0

15 Apr 21:37
Immutable release. Only release title and notes can be modified.
3c0c8a9

Choose a tag to compare

  • Switch default branch from main to latest so npm create tags align with the branch name
  • Update all workflow triggers, release config, install script, and raw GitHub URLs to reference latest
  • Add latest to recognized base branch names in development-workflows config
  • Bump fallback default branch from main to latest in dev_sync

Release v0.5.1

15 Apr 21:18
Immutable release. Only release title and notes can be modified.
404bb13

Choose a tag to compare

  • Fix absolute local paths leaking into context.yaml and AGENTS.md refs
  • Use GitHub tree URLs for directory refs, raw URLs for file refs
  • Add cross-repo-issue-context practice from learned agent sessions
  • Filter placeholder URLs (test/repo, org/repo) from learned references
  • Add regression test for absolute path prevention

Release v0.5.0

14 Apr 21:58
Immutable release. Only release title and notes can be modified.
d237ce2

Choose a tag to compare

  • Slim factors from 7 to 4: documentation, dependencies, config, pipeline
  • Drop architecture, runtime, build_release_run — dev.kit detects repo/CI/CD signals, not app structure
  • Merge test commands and deploy config into single pipeline factor
  • Widen workflow tracing: catch direct actions (uses: org/repo@ref), docker actions, workflow images
  • Resolve Docker images to same-org source repos (Docker Hub org ≠ GitHub org matching)
  • Simplify documentation factor to binary present/missing
  • Simplify README as pitch + quick start, move deep details to docs/
  • Add bot feedback loop practice for PR reviews

Release v0.4.0

14 Apr 20:52
Immutable release. Only release title and notes can be modified.
a1df982

Choose a tag to compare

  • Add structured dependency resolution with cross-repo tracing
  • Resolve same-org dependencies via gh api and sibling directory lookup
  • Track file-level relationships (used_by) mapping current repo files to their dependencies
  • Trace 6 dependency sources: workflow reuse, Docker images, Compose images, versioned YAML configs, GitHub URLs, npm packages
  • Add --force flag to dev.kit repo for full dependency re-resolution
  • Include structured dependencies in JSON output (repo.json, agent.json)
  • Render dependency relationships in AGENTS.md with resolved metadata and source file mappings
  • Add dependency_trace_compose_files and dependency_trace_url_globs to detection-signals.yaml