diff --git a/.github/workflows/pythonpublish.yml b/.github/workflows/pythonpublish.yml index d44bf7f..eca62f5 100644 --- a/.github/workflows/pythonpublish.yml +++ b/.github/workflows/pythonpublish.yml @@ -6,7 +6,7 @@ on: permissions: id-token: write # This is required for requesting the JWT - contents: read + contents: write jobs: deploy: @@ -15,14 +15,17 @@ jobs: steps: - uses: actions/checkout@v4 + with: + fetch-depth: 0 - uses: actions/setup-node@v4 with: - node-version: 18 + node-version: 'lts/*' - run: npx changelogithub continue-on-error: true env: GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}} + - name: Set up Python uses: actions/setup-python@v5 with: diff --git a/doc/src/plugins/backend.rst b/doc/src/plugins/backend.rst index d9ec08b..84f76e1 100644 --- a/doc/src/plugins/backend.rst +++ b/doc/src/plugins/backend.rst @@ -10,8 +10,12 @@ To set it up, a few configuration steps are required. Lockfile configuration ====================== -Your lockfile must be configured with the ``include_metadata`` strategy (``pdm>=2.11``) and include locks for the -optional-dependencies groups you want to publish locked. +Your lockfile must be configured with the ``inherit_metadata`` strategy (``pdm>=2.11``) and include locks for the optional-dependencies groups you want to publish locked. + + .. note:: + When running ``pdm lock``, ensure you select the appropriate dependency groups. + + For instance, you can use ``pdm lock -G :all`` and then verify that the ``[metadata]`` section of the ``pdm.lock`` file includes the desired groups. For more details, refer to the ``Dependencies Selection:`` section in the ``pdm lock --help`` output. buildsystem configuration ========================= @@ -51,6 +55,7 @@ By default, the default group and all optional groups will be locked, but you ca .. code-block:: toml :caption: pyproject.toml + # for pdm-backend [tool.pdm.build] locked = true