Skip to content

chore: migrate release-doc-sync pin from @v1.0 to @v1#8

Merged
TMHSDigital merged 1 commit intomainfrom
chore/migrate-release-doc-sync-to-v1
Apr 25, 2026
Merged

chore: migrate release-doc-sync pin from @v1.0 to @v1#8
TMHSDigital merged 1 commit intomainfrom
chore/migrate-release-doc-sync-to-v1

Conversation

@TMHSDigital
Copy link
Copy Markdown
Owner

One-line migration: bumps the release-doc-sync action pin from @v1.0 to @v1.

The v1 floating tag is auto-maintained by the meta-repo's release.yml since DTD#14 landed (PR #26). v1.0 was a legacy float created before that automation existed.

Once all 6 consumer repos migrate, v1.0 will be deleted in the meta-repo.

Refs TMHSDigital/Developer-Tools-Directory#27.

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
@github-actions github-actions Bot added the ci label Apr 25, 2026
@TMHSDigital TMHSDigital merged commit e97ca00 into main Apr 25, 2026
12 checks passed
@TMHSDigital TMHSDigital deleted the chore/migrate-release-doc-sync-to-v1 branch April 25, 2026 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant