diff --git a/README.md b/README.md index 6859f24..998aaf5 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,7 @@ bedrock-python/clientwright, … the libraries: topic python, subscr | `claude` | Claude Code instructions, settings, skills and a reviewer agent | the template's starter pack | | `python-library` | guidelines for public APIs, versioning and deprecation | the template's starter pack | -The first two packs are the files python-library-template gives every new library, taken from its `template/` directory at commit `a1a1e7d` (`CODE_OF_CONDUCT.md` from the repository root, which is the rendered `CODE_OF_CONDUCT.md.jinja`). Their blob ids are the ones the libraries already have, so for every library that never changed them, touchmark recognises them as shipped and connects them with an empty diff. Keep python-library-template and these packs in step: a change goes to the pack here, and the same bytes to the template, so new libraries start in sync. The first such change, on 2026-10-07: `docs.yml` takes clientwright's `workflow_dispatch`, `concurrency: pages` and `--no-dev --group docs` on `uv run`, and pg-partsmith's `uv sync --locked`. +The first two packs are the files python-library-template gives every new library, taken from its `template/` directory at commit `a1a1e7d` (`CODE_OF_CONDUCT.md` from the repository root, which is the rendered `CODE_OF_CONDUCT.md.jinja`). Their blob ids are the ones the libraries already have, so for every library that never changed them, touchmark recognises them as shipped and connects them with an empty diff. Keep python-library-template and these packs in step: a change goes to the pack here, and the same bytes to the template, so new libraries start in sync. The first such change, on 2026-10-07: `docs.yml` takes clientwright's `workflow_dispatch`, `concurrency: pages` and `--no-dev --group docs` on `uv run`, and pg-partsmith's `uv sync --locked`. The second, on 2026-11-15: `release-please.yml` takes python-library-template#23, a token of the org's release App so that CI runs on release pull requests. Every library had already taken it from the template on 2026-10-17, which made their copies their own; they are the same bytes as the pack now, so they are the hub's again. `targets.yml` selects the libraries created from python-library-template, the organisation's repositories with the topic `python` but mr-review, the blog and the template itself, and gives each all five packs. The libraries share one owner with the hub, so the hub subscribes them itself (`opt_in: assumed`) instead of waiting for an `.engineering-assets.yml` in each; a library chooses packs or ignores files by adding that file, and opts out with `enabled: false` in it. The subscription rolled out in two steps ([Rollout](#rollout)): deadline-budget first, then every library. diff --git a/packs/bedrock-community/.github/workflows/release-please.yml b/packs/bedrock-community/.github/workflows/release-please.yml index 8947d93..5b29311 100644 --- a/packs/bedrock-community/.github/workflows/release-please.yml +++ b/packs/bedrock-community/.github/workflows/release-please.yml @@ -12,7 +12,31 @@ jobs: release-please: runs-on: ubuntu-latest steps: + # A pull request opened or updated with GITHUB_TOKEN does not get a CI run + # that ever starts, so the release PR could not pass its required check + # until a person closed and reopened it. A token of the org's release App + # starts CI like anyone else's push. Until the App is set up, GITHUB_TOKEN + # is used and the run says so. Setup, once per org: + # https://github.com/bedrock-python/python-library-template#the-release-app + - name: Token from the release App + id: app + if: vars.RELEASE_PLEASE_APP_CLIENT_ID != '' + uses: actions/create-github-app-token@v3 + with: + client-id: ${{ vars.RELEASE_PLEASE_APP_CLIENT_ID }} + private-key: ${{ secrets.RELEASE_PLEASE_APP_PRIVATE_KEY }} + permission-contents: write + permission-pull-requests: write + + - name: No release App + if: steps.app.outcome == 'skipped' + run: >- + echo "::warning::RELEASE_PLEASE_APP_CLIENT_ID is not set, so the release PR + is opened with GITHUB_TOKEN and CI will not run on it: close and reopen it + right before merging." + - uses: googleapis/release-please-action@v5 with: + token: ${{ steps.app.outputs.token || github.token }} config-file: release-please-config.json manifest-file: .release-please-manifest.json