feat: integrate release-doc-sync to keep release docs aligned#26
Merged
TMHSDigital merged 1 commit intomainfrom Apr 25, 2026
Merged
feat: integrate release-doc-sync to keep release docs aligned#26TMHSDigital merged 1 commit intomainfrom
TMHSDigital merged 1 commit intomainfrom
Conversation
…MAP aligned Adds the release-doc-sync@v1.0 composite action from the meta-repo to release.yml. After plugin.json is bumped on auto-release, the action edits CHANGELOG.md, CLAUDE.md, and ROADMAP.md to reflect the new version. The existing commit-and-tag step picks up the doc changes. Smoke test for Phase 2b of TMHSDigital/Developer-Tools-Directory#5 resolution. After this PR merges, the next auto-release will exercise the action end-to-end. Subsequent PRs should see the doc-consistency tests pass. Refs TMHSDigital/Developer-Tools-Directory#5. Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com Made-with: Cursor
Contributor
Dependency ReviewThe following issues were found:
License Issues.github/workflows/release.yml
OpenSSF Scorecard
Scanned Files
|
TMHSDigital
added a commit
that referenced
this pull request
Apr 25, 2026
…28) The test asserted that ROADMAP.md's table marks the current plugin.json version as (current). Per the standards/versioning.md policy adopted in Developer-Tools-Directory v1.8.0, patch releases do NOT get themed roadmap table rows; rows are reserved for minor and major releases that have thematic content. The test was therefore checking for behavior we explicitly do not want. Removing it aligns CI with policy. The complementary test_changelog_has_current_version remains and now passes thanks to release-doc-sync@v1.0 (integrated in PR #26, Phase 2b/2c work). Closes #25. 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
This was referenced Apr 25, 2026
TMHSDigital
added a commit
that referenced
this pull request
Apr 25, 2026
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
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.
Integrates the
release-doc-sync@v1.0composite action fromTMHSDigital/Developer-Tools-Directoryinto Docker'srelease.yml.The action runs inside
release.ymlafterplugin.jsonis bumped, editingCHANGELOG.md,CLAUDE.md, andROADMAP.mdto reflect the new version. The existing commit-and-tag step picks up the doc changes.This is the smoke test for Phase 2b of the doc-consistency cluster resolution (
TMHSDigital/Developer-Tools-Directory#5). After this PR merges, the next auto-release will exercise the action end-to-end.The PR's own CI does NOT exercise
release-doc-syncdirectly — the action only runs as part ofrelease.ymlon push tomain. The PR's CI validates the workflow YAML and the integration shape.What the new step does
Runs between "Update version files" (which bumps
plugin.json+ the README badge) and "Commit and tag" (whichgit add -Apicks up the doc edits).Refs
TMHSDigital/Developer-Tools-Directory#5.