-
Notifications
You must be signed in to change notification settings - Fork 0
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
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/Unity-Developer-Tools
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.4.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: TMHSDigital/Unity-Developer-Tools
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.4.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 5 commits
- 38 files changed
- 2 contributors
Commits on Apr 25, 2026
-
chore: bump GitHub Actions to Node 24-compatible versions (#9)
GitHub Actions is forcing Node 24 as the default runtime on 2026-06-02. This bumps actions still on Node 20 to versions that support Node 24: - actions/checkout v4/v5 -> v6 - actions/setup-python v5 -> v6 - actions/setup-node v4 -> v6 - actions/upload-pages-artifact v3/v4 -> v5 - actions/configure-pages v5 -> v6 - actions/deploy-pages v4 -> v5 - actions/labeler v5 -> v6 - actions/stale v9 -> v10 - softprops/action-gh-release v2 -> v3 - release-drafter/release-drafter v6 -> v7 - github/codeql-action/* v3 -> v4 - peter-evans/create-pull-request v6 SHA -> v8.1.1 SHA (DTD only) actions/dependency-review-action remains at v4 (upstream-blocked at Node 20; tracked in TMHSDigital/Developer-Tools-Directory#32). Refs TMHSDigital/Developer-Tools-Directory#18. Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com Made-with: Cursor Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com
Configuration menu - View commit details
-
Copy full SHA for ee195f2 - Browse repository at this point
Copy the full SHA ee195f2View commit details -
chore: add github-actions ecosystem to dependabot coverage (#10)
This repo lacked dependabot coverage for the github-actions ecosystem, which is how the Node 20 deprecation accumulated silently before DTD#18 surfaced it as a deadline-driven scramble. Adds .github/dependabot.yml with weekly github-actions update checks. Future deprecations will surface as PRs rather than needing manual ecosystem audits. Refs TMHSDigital/Developer-Tools-Directory#31. Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com Made-with: Cursor Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com
Configuration menu - View commit details
-
Copy full SHA for 3adf878 - Browse repository at this point
Copy the full SHA 3adf878View commit details
Commits on Apr 26, 2026
-
chore: bump standards-version signals and drift-check pin to 1.9.0 (#11)
Aligns this repo with the meta-repo's current MINOR (v1.9.x). Two coupled changes: 1. Signal bump: standards-version 1.7.0 -> 1.9.0 across all SKILL.md, .mdc, AGENTS.md (where present), and CLAUDE.md (where present) files. 2. Workflow pin: drift-check@v1.<old> -> drift-check@v1.9. Per Phase 2 Design Decision 1, drift-check consumers track explicit MINOR for deliberate standards version awareness. Each MINOR represents a meaningful standards revision; tool repos signal which revision they are aligned with via the signal version, and consume the matching action via explicit MINOR pin. The actual purpose of this rollout is to align ecosystem signals with current MINOR so the (now-active per DTD#12) stale-counts checker is exercised against current standards, and so the meta-repo's mode: all drift-check reads consistent versions across the ecosystem. Refs TMHSDigital/Developer-Tools-Directory#12. Made-with: Cursor Signed-off-by: TMHSDigital <154358121+TMHSDigital@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 903511a - Browse repository at this point
Copy the full SHA 903511aView commit details -
fix: remove paths-ignore from release.yml so content edits fire relea…
…se pipeline (#12) Tracks DTD#47. Parallel rollout following Home-Lab canary at b7adc86. The previous paths-ignore excluded content paths from release triggers, silently preventing content additions and AGENTS.md/CLAUDE.md edits from firing release-doc-sync reconciliation. Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for 5d790cf - Browse repository at this point
Copy the full SHA 5d790cfView commit details -
Configuration menu - View commit details
-
Copy full SHA for f01579b - Browse repository at this point
Copy the full SHA f01579bView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.4.1...v1.4.2