mirror of
https://github.com/jason5ng32/MyIP.git
synced 2026-11-04 18:23:27 +00:00
Both actions published v6 in late 2024/early 2025 with `runs.using: node24` declared natively, so they no longer emit the Node 20 deprecation warning nor need the `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24` env-var opt-in that the previous commit added. Upgrading directly is cleaner than keeping the workaround and lets the workflow files shed the accompanying comment blocks. No breaking changes affect this project's usage (checkout + setup-node with `node-version` only). The third-party `aormsby/Fork-Sync-With-Upstream-action@v3.4` in sync.yml has shipped on node24 since v3.4.2, so no env-var fallback is needed there either. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
41 lines
1.2 KiB
YAML
41 lines
1.2 KiB
YAML
name: Upstream Sync
|
|
|
|
permissions:
|
|
contents: write
|
|
|
|
on:
|
|
schedule:
|
|
- cron: "0 0 * * *" # every day at 00:00 UTC
|
|
workflow_dispatch:
|
|
|
|
jobs:
|
|
sync_latest_from_upstream:
|
|
name: Sync latest commits from upstream repo
|
|
runs-on: ubuntu-latest
|
|
if: ${{ github.event.repository.fork }}
|
|
|
|
steps:
|
|
# step 1: checkout target repo
|
|
- name: Checkout target repo
|
|
uses: actions/checkout@v6
|
|
|
|
# step 2: sync upstream changes
|
|
- name: Sync upstream changes
|
|
id: sync
|
|
uses: aormsby/Fork-Sync-With-Upstream-action@v3.4
|
|
with:
|
|
upstream_sync_repo: jason5ng32/MyIP
|
|
upstream_sync_branch: main
|
|
target_sync_branch: main
|
|
target_repo_token: ${{ secrets.GITHUB_TOKEN }} # auto-generated, no need to set
|
|
|
|
# set test_mode to true to run tests instead of the real action!
|
|
test_mode: false
|
|
|
|
# error check
|
|
- name: Sync check
|
|
if: failure()
|
|
run: |
|
|
echo "[Error] Due to a change in the workflow file of the upstream repository, GitHub has automatically suspended the scheduled automatic update. You need to manually sync your fork again."
|
|
exit 1
|