Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: TMHSDigital/Docker-Developer-Tools
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.3.3
Choose a base ref
...
head repository: TMHSDigital/Docker-Developer-Tools
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.3.4
Choose a head ref
  • 5 commits
  • 7 files changed
  • 3 contributors

Commits on Apr 25, 2026

  1. chore: backfill stale doc references after Phase 2 doc-consistency ro…

    …llout (#29)
    
    The release-doc-sync action (Developer-Tools-Directory v1.8.x) was
    integrated in Phase 2c and now auto-maintains CHANGELOG.md and
    CLAUDE.md on each release. The existing gap between v1.0.0 and v1.3.x
    (current) was not auto-filled.
    
    This PR bridges that gap with honest documentation:
    - CHANGELOG.md gets a single "[Versions 1.0.1 through 1.2.x]"
      entry pointing to GitHub releases
    - CLAUDE.md hardcoded version references updated to current
    - standards-version marker preserved
    
    No code or workflow changes. Documentation only.
    
    Refs TMHSDigital/Developer-Tools-Directory#5.
    
    Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com
    Made-with: Cursor
    
    Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com
    TMHSDigital authored Apr 25, 2026
    Configuration menu
    Copy the full SHA
    a696b77 View commit details
    Browse the repository at this point in the history
  2. fix: port Unity's self-healing pattern to label-sync workflow (#30)

    The workflow's apply step expected labels to exist, failing PR runs
    when path-mapped labels (skills, rules, mcp-server, ci) were missing
    from the repo. This port replaces the apply step with the per-label
    loop that uses `gh label create --force` before `gh pr edit --add-label`,
    making label creation idempotent.
    
    Phase 2b parallel rollout following the Home-Lab canary
    (TMHSDigital/Home-Lab-Developer-Tools#16).
    
    Refs TMHSDigital/Developer-Tools-Directory#4.
    
    Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com
    Made-with: Cursor
    
    Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com
    TMHSDigital authored Apr 25, 2026
    Configuration menu
    Copy the full SHA
    ad73691 View commit details
    Browse the repository at this point in the history
  3. chore: migrate release-doc-sync pin from @v1.0 to @v1 (#31)

    The v1.0 floating tag was created in Phase 2a (PR #19) before
    automated floating-tag maintenance existed. PR #26 (DTD#14) added
    automation that maintains v1 (vMAJOR) and v1.8 (vMAJOR.MINOR)
    floating tags on every release. v1 now serves the purpose v1.0
    was created for.
    
    Migrating to @v1 makes this repo's release-doc-sync integration
    consistent with the auto-maintained tag namespace and removes the
    last consumer of the legacy v1.0 tag (once all 6 consumers
    migrate, v1.0 will be deleted).
    
    Refs TMHSDigital/Developer-Tools-Directory#27.
    
    Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com
    Made-with: Cursor
    
    Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com
    TMHSDigital authored Apr 25, 2026
    Configuration menu
    Copy the full SHA
    37f0a2a View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    0dbcbcb View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    0c06538 View commit details
    Browse the repository at this point in the history
Loading