Skip to content

Promote the Hub Resync From develop to main #132

Description

@ptr727

The hub resync (#127, #128, #129, #130, and #131) is on develop and not yet on main. Consumers pull latest from main, and the Docker Hub overview and short description publish only from main, so the resync's effect is incomplete until the promotion.

Promotion Notes

  • Expected conflict: Dependabot updated .github/workflows/build-docker-task.yml, build-release-task.yml, get-version-task.yml, publish-docker-readme-task.yml, and validate-task.yml on main, and develop deletes them (Adopt the Hub Reusable Workflows and Retire repo-config #129). The promotion shows a modify/delete conflict on each. Resolve it by keeping the deletion, since the thin callers reach the hub's copies instead.
  • After the merge: the next main publish, the weekly schedule or a dispatch, pushes the About text to Docker Hub as the short description. That clears the last audit finding.
  • Cleanup: the five resync/* branches remain on the remote, since branch auto-delete is off. Delete them once the promotion lands.

Put Closes keywords for any develop-only issue in the promotion PR's description, since they fire only on a merge to main.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreRegistry, labels, rollout, and other fleet housekeeping

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions