diff --git a/.github/dependabot.yml b/.github/dependabot.yml deleted file mode 100644 index 3a3cce5763..0000000000 --- a/.github/dependabot.yml +++ /dev/null @@ -1,11 +0,0 @@ -# To get started with Dependabot version updates, you'll need to specify which -# package ecosystems to update and where the package manifests are located. -# Please see the documentation for all configuration options: -# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates - -version: 2 -updates: - - package-ecosystem: "npm" # See documentation for possible values - directory: "/" # Location of package manifests - schedule: - interval: "weekly" diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 2a41330948..765c1fab64 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -1,3 +1,8 @@ +# Tests only. This repo no longer publishes to npm: its packages are published from +# pie-framework/pie-elements-ng, which takes over their npm trusted-publisher records +# (PIE-883). npm allows one trusted publisher per package, so once this repo's records are +# revoked, a publish from here would fail with ENEEDAUTH; the publish jobs are removed so a +# merge cannot attempt one. They remain in git history. name: PIE Elements CI on: @@ -6,11 +11,6 @@ on: pull_request: branches: [develop, master] workflow_dispatch: - inputs: - ref: - description: Branch or commit to publish missing packages from - required: false - default: master jobs: test: @@ -31,120 +31,3 @@ jobs: - run: scripts/release --build - run: scripts/release --test - build-next: - needs: test - if: > - github.event_name == 'push' && - github.ref == 'refs/heads/develop' - runs-on: ubuntu-latest - permissions: - contents: write - id-token: write # REQUIRED for npm trusted publishing - steps: - - uses: actions/checkout@v5 - with: - fetch-depth: 0 # REQUIRED for lerna version - - name: Configure Git - run: | - git config user.name "github-actions[bot]" - git config user.email "41898282+github-actions[bot]@users.noreply.github.com" - - uses: actions/setup-node@v5 - with: - node-version: 24 - registry-url: https://registry.npmjs.org/ - cache: yarn - - run: yarn install - - run: scripts/release --build - - run: scripts/release --release --next --loglevel verbose - - # Versioning is split from publishing deliberately. `lerna version` is cheap - # and reliable; publishing depends on the registry plus the sigstore services - # behind provenance, and a transient failure there used to take the whole - # release down with it. Because `publish` checks out the commit `version` - # pushed — rather than the commit that triggered the run, which predates the - # bump — "Re-run failed jobs" re-runs only the publish, against the correct - # versions, and picks up whatever is still missing from the registry. - version: - needs: test - if: > - github.event_name == 'push' && - github.ref == 'refs/heads/master' - runs-on: ubuntu-latest - permissions: - contents: write # REQUIRED to push the version commit and tags - outputs: - sha: ${{ steps.versioned.outputs.sha }} - steps: - - uses: actions/checkout@v5 - with: - fetch-depth: 0 # REQUIRED for lerna version - - name: Configure Git - run: | - git config user.name "github-actions[bot]" - git config user.email "41898282+github-actions[bot]@users.noreply.github.com" - - uses: actions/setup-node@v5 - with: - node-version: 24 - cache: yarn - - run: yarn install - - run: scripts/release --bump - - id: versioned - run: echo "sha=$(git rev-parse HEAD)" >> "$GITHUB_OUTPUT" - - publish: - needs: version - runs-on: ubuntu-latest - permissions: - contents: read - id-token: write # REQUIRED for npm trusted publishing - steps: - - uses: actions/checkout@v5 - with: - ref: ${{ needs.version.outputs.sha }} - fetch-depth: 0 # REQUIRED for lerna to describe the working tree - - name: Configure Git - run: | - git config user.name "github-actions[bot]" - git config user.email "41898282+github-actions[bot]@users.noreply.github.com" - - uses: actions/setup-node@v5 - with: - node-version: 24 - registry-url: https://registry.npmjs.org/ - cache: yarn - - run: yarn install - - run: scripts/release --build - - run: scripts/release --publish --loglevel verbose - - # Manually-triggered retry: publishes only package versions that are missing - # from the registry (lerna publish from-package), skipping already-published - # ones. Use this to finish a release where some packages failed to publish - # (e.g. a transient npm provenance/transparency-log error) without re-running - # `lerna version`. - publish-missing: - needs: test - if: github.event_name == 'workflow_dispatch' - runs-on: ubuntu-latest - permissions: - contents: read - id-token: write # REQUIRED for npm trusted publishing - steps: - - uses: actions/checkout@v5 - with: - ref: ${{ github.event.inputs.ref }} - fetch-depth: 0 - - name: Configure Git - run: | - git config user.name "github-actions[bot]" - git config user.email "41898282+github-actions[bot]@users.noreply.github.com" - - uses: actions/setup-node@v5 - with: - node-version: 24 - registry-url: https://registry.npmjs.org/ - cache: yarn - - run: yarn install - - run: scripts/release --build - # Invoke lerna directly (not via scripts/release) so this step does not - # depend on the scripts/release version present on the checked-out ref. - # `from-package` publishes only versions missing from the registry and - # never versions or pushes tags, so it needs no write access to the repo. - - run: npx lerna publish from-package --yes --loglevel verbose diff --git a/README.md b/README.md index 5221f36f3e..db8532ba48 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,10 @@ # pie-elements +> [!IMPORTANT] +> This repository is no longer maintained. Development and npm publishing for +> `@pie-element/*` have moved to +> [pie-elements-ng](https://github.com/pie-framework/pie-elements-ng). + A collection of pies. These packages are pie packages in that they have an optional `configure` and/or `controller` sub package. ## Install