Adopt framework v0.6.0 and call the shared script from the publish workflow #112
@@ -68,23 +68,11 @@ jobs:
|
||||
git submodule update --init --recursive --depth=1
|
||||
|
||||
- name: Make sure curl and jq are available
|
||||
run: |
|
||||
set -euo pipefail
|
||||
if command -v curl >/dev/null && command -v jq >/dev/null; then exit 0; fi
|
||||
sudo_cmd=""
|
||||
if [ "$(id -u)" -ne 0 ]; then sudo_cmd="sudo"; fi
|
||||
$sudo_cmd apt-get update -qq
|
||||
$sudo_cmd apt-get install -y -qq curl jq
|
||||
run: bash framework/scripts/ci-publish-milestones.sh ensure-tools
|
||||
|
||||
- name: Publish accepted milestones
|
||||
env:
|
||||
GITEA_TOKEN: ${{ secrets.TOKEN_FOR_GITEA }}
|
||||
# Empty on a push (a real run); "true" or "false" on a manual run.
|
||||
DRY_RUN: ${{ inputs.dry_run }}
|
||||
run: |
|
||||
set -euo pipefail
|
||||
if [ "$DRY_RUN" = "true" ]; then
|
||||
bash framework/scripts/sync-project.sh --accepted-only
|
||||
else
|
||||
bash framework/scripts/sync-project.sh --accepted-only --apply
|
||||
fi
|
||||
run: bash framework/scripts/ci-publish-milestones.sh publish
|
||||
|
||||
@@ -26,6 +26,10 @@ Each release lists its changes in these groups, in this order:
|
||||
runner for the host's default limit.
|
||||
- `actions/checkout` is referenced by the exact tag `v4.2.2` instead of the
|
||||
moving tag `v4`. No change for callers.
|
||||
- The framework pin moves from `v0.5.2` to `v0.6.0`, and the two long `run:`
|
||||
blocks of this repository's own `sync-milestones.yml` call
|
||||
`framework/scripts/ci-publish-milestones.sh`. No change for callers of the
|
||||
shared workflows.
|
||||
|
||||
## [1.1.0] - 2026-10-11
|
||||
|
||||
|
||||
+1
-1
Submodule framework updated: 4fd69c4970...2b4a058f26
Reference in New Issue
Block a user