This temporarily reverts commit 4c0e95b73c
to make PRs based on a branch with the older workflow still pass.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
The milestone check reads the next versions from the pinned branch
status issue now, and nothing else uses this file.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Like shell globs, git's pathspec * does not match files or directories
whose names begin with ., so hidden files such as .dockerignore,
.gitignore, and everything under .github/ would not be checked out from
the tag when resolving a merge conflict.
This means those files retain the conflict-state version, and the
subsequent git add --all + git merge --continue would commit the wrong
content for those paths.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
The sed address /${tag}/q treated the tag as a regex, so dots in
version strings like docker-v27.3.1 matched any character.
Replace sed with awk using a -v variable and a literal string comparison
($0==tag) so the tag is never interpreted as a regex pattern.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Prefer upstream/master when available (local development), but fall
back to origin/master so the script works in CI where actions/checkout
only sets up an origin remote.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Add a manually dispatched workflow for maintainers to sync a docker
release branch to a selected docker release tag.
The job checks out the requested release branch, merges the tag with
`git merge --no-ff`, checks the worktree content out from that tag,
stages the result, and pushes the updated branch.
The actual push is guarded by the `docker-releases` GitHub environment
which requires a manual approval.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Rename the release metadata key from current to last so it describes the
version it stores more accurately.
The value represents the most recent completed Docker release, while
next continues to track the upcoming release.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Add validation to ensure PRs have milestones set and that they match the
expected docker next version defined in releases configuration.
This prevents PRs from being merged without proper milestone tracking,
which is important for release management and ensuring changes are
properly categorized for upcoming releases.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Paweł Gronowski