From 79eda5e77df2880f26978bcb4a432eeaace31abb Mon Sep 17 00:00:00 2001 From: Steve Juma Date: Sun, 15 Nov 2026 19:13:32 +0000 Subject: [PATCH] Retire profile token writer for the central App pilot --- .github/workflows/refresh-npm-status.yml | 53 +----------------------- README.md | 16 +++++-- 2 files changed, 14 insertions(+), 55 deletions(-) diff --git a/.github/workflows/refresh-npm-status.yml b/.github/workflows/refresh-npm-status.yml index e6f61d9..4fd7ac8 100644 --- a/.github/workflows/refresh-npm-status.yml +++ b/.github/workflows/refresh-npm-status.yml @@ -1,8 +1,6 @@ name: Refresh npm status on: - schedule: - - cron: "23 * * * *" workflow_dispatch: push: branches: [main] @@ -31,56 +29,9 @@ jobs: timeout-minutes: 5 steps: - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6 - - uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6 with: - node-version: "24" - - run: node --test scripts/update-npm-status.test.mjs - - refresh: - if: github.event_name != 'pull_request' - needs: check - runs-on: ubuntu-latest - timeout-minutes: 5 - permissions: - contents: write - pull-requests: write - steps: - - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6 + persist-credentials: false - uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6 with: node-version: "24" - - run: node scripts/update-npm-status.mjs - - name: Open or update the package status pull request - env: - GH_TOKEN: ${{ github.token }} - run: | - set -euo pipefail - if git diff --quiet -- profile/README.md; then - echo "No npm status changes to publish." - exit 0 - fi - - branch="automation/npm-status-refresh" - git config user.name "github-actions[bot]" - git config user.email "41898282+github-actions[bot]@users.noreply.github.com" - git add profile/README.md - git commit -m "Refresh npm publication status and versions" - - if git fetch origin "refs/heads/$branch:refs/remotes/origin/$branch"; then - lease="$(git rev-parse "refs/remotes/origin/$branch")" - git push --force-with-lease="refs/heads/$branch:$lease" origin "HEAD:refs/heads/$branch" - else - git push origin "HEAD:refs/heads/$branch" - fi - - pr_number="$(gh pr list --repo "$GITHUB_REPOSITORY" --head "$branch" --base main --state open --json number --jq '.[0].number // empty')" - if [[ -n "$pr_number" ]]; then - echo "Updated npm status pull request #$pr_number." - else - gh pr create \ - --repo "$GITHUB_REPOSITORY" \ - --head "$branch" \ - --base main \ - --title "Refresh npm publication status and versions" \ - --body "Automated refresh of the organization profile from the public npm registry." - fi + - run: node --test scripts/update-npm-status.test.mjs diff --git a/README.md b/README.md index 3f3df2f..6adf77a 100644 --- a/README.md +++ b/README.md @@ -21,10 +21,18 @@ registry's `latest` versions, and `node --test scripts/update-npm-status.test.mj to check the updater. [Refresh npm status](https://github.com/lapismd/.github/actions/workflows/refresh-npm-status.yml) -runs hourly, on updater changes, and on manual dispatch. It opens or updates one -automation pull request when package status changes. Registry errors fail the -refresh and preserve the previous profile; a registry 404 is the only response -treated as unpublished. +runs updater tests on changes and manual dispatch. The generator remains owned +here; the old scheduled GITHUB_TOKEN writer is retired to avoid competing PR +writers and workflow-approval waits. + +[The central profile pilot](https://github.com/lapismd/dependency-automation/actions/workflows/profile-refresh.yml) +generates the candidate without App credentials, then validates and publishes +only npm-status cells through a separate worker using the existing App. It keeps +one rolling PR, stops for manual branch repairs, and preserves ordinary CI and +merge policy. The pilot is manual-only until hosted acceptance is recorded in +[the rollout tracker](https://github.com/lapismd/dependency-automation/blob/main/PLAN.md). +No secret is copied to this repository. Registry errors preserve the previous +profile; a registry 404 is the only response treated as unpublished. This repository contains organization profile documentation only. It does not configure CI, publishing, or policy for the other repositories.