build(deps): bump poetry-dynamic-versioning from 0.25.0 to 1.7.0 in /.github/workflows

[dependabot]

Bumps poetry-dynamic-versioning from 0.25.0 to 1.7.0.

Release notes

Sourced from poetry-dynamic-versioning's releases.

v1.7.0 (2025-01-15)

• Added:
  • The enable command now supports the bypass/override environment variables to use a different placeholder version than 0.0.0.
• Fixed:
  • The enable command would add "version" to project.dynamic even if it were already present. (Contributed by waketzheng)
  • The enable command would set tool.poetry.version to "0.0.0" even if the field were already present with a different value.

v1.6.0 (2025-01-10)

• Added:
  • CLI: show command to print the version without changing any files.

v1.5.2 (2025-01-09)

• Fixed:
  • The formatting of project.dynamic and tool.poetry.version could be changed when triggering the plugin via poetry dynamic-versioning or pip install (but not via poetry build or poetry-dynamic-versioning).

v1.5.1 (2025-01-09)

• Fixed:
  • Array formatting was not preserved when changing project.dynamic in pyproject.toml. (Contributed by edgarrmondragon)

v1.5.0 (2025-01-05)

• Added:
  • CLI: When pyproject.toml contains the project section, the enable command will add the required fields for Poetry 2.0.0+.
• Fixed:
  • For compatibility with Poetry 2.0.0, adjusted Poetry constraint from ^1.2.0 to >=1.2.0.
  • For compatibility with Poetry 2.0.0, when inserting the dynamic version into pyproject.toml with PEP 621 mode activated, the plugin ensures not to set project.version and tool.poetry.version at the same time.
  • An UnboundLocalError could happen when pyproject.toml was misconfigured.

v1.4.1 (2024-09-10)

• Fixed:
  • The enable command would fail when the pyproject.toml tables were out of order.

v1.4.0 (2024-06-17)

• Added:

  • The plugin now supports Poetry's upcoming PEP-621 functionality. More info here: python-poetry/poetry#3332

    If your pyproject.toml defines tool.poetry.name, then the plugin will preserve its existing behavior.

    However, if your pyproject.toml:

    • does not define tool.poetry.name
    • defines project.name
    • defines project.dynamic to include "version"
    • does not define project.version

    ...then the plugin will enable its PEP-621 functionality.

    Because PEP-621 support is not yet released and finalized in Poetry itself, it is also subject to change in the plugin.

    (Prototyped by edgarrmondragon)

... (truncated)

Changelog

Sourced from poetry-dynamic-versioning's changelog.

v1.7.0 (2025-01-15)

• Added:
  • The enable command now supports the bypass/override environment variables to use a different placeholder version than 0.0.0.
• Fixed:
  • The enable command would add "version" to project.dynamic even if it were already present. (Contributed by waketzheng)
  • The enable command would set tool.poetry.version to "0.0.0" even if the field were already present with a different value.

v1.6.0 (2025-01-10)

• Added:
  • CLI: show command to print the version without changing any files.

v1.5.2 (2025-01-09)

• Fixed:
  • The formatting of project.dynamic and tool.poetry.version could be changed when triggering the plugin via poetry dynamic-versioning or pip install (but not via poetry build or poetry-dynamic-versioning).

v1.5.1 (2025-01-09)

• Fixed:
  • Array formatting was not preserved when changing project.dynamic in pyproject.toml. (Contributed by edgarrmondragon)

v1.5.0 (2025-01-05)

• Added:
  • CLI: When pyproject.toml contains the project section, the enable command will add the required fields for Poetry 2.0.0+.
• Fixed:
  • For compatibility with Poetry 2.0.0, adjusted Poetry constraint from ^1.2.0 to >=1.2.0.
  • For compatibility with Poetry 2.0.0, when inserting the dynamic version into pyproject.toml with PEP 621 mode activated, the plugin ensures not to set project.version and tool.poetry.version at the same time.
  • An UnboundLocalError could happen when pyproject.toml was misconfigured.

v1.4.1 (2024-09-10)

• Fixed:
  • The enable command would fail when the pyproject.toml tables were out of order.

v1.4.0 (2024-06-17)

• Added:

... (truncated)

Commits

• 7e60328 Release v1.7.0
• 017a1b1 Support override env var for 'enable' command
• b5e1e7d #214: Update changelog
• c4d7669 Merge pull request #214 from waketzheng/master
• 948d3a9 Fix cli add "version" into dynamic array even already included
• 188beee Release v1.6.0
• 3510a6f #210: Add 'show' command
• ebb3908 Release v1.5.2
• 4d26f8b #203: Prevent formatting change in some commands
• bbeebe9 Release v1.5.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #471.