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

[dependabot]

Bumps poetry-dynamic-versioning from 0.25.0 to 1.4.0.

Release notes

Sourced from poetry-dynamic-versioning's releases.

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)

v1.3.0 (2024-04-29)

• Added:
  • pattern-prefix option to add a prefix to the version tag pattern.
  • ignore-untracked option to control the detection of dirty state.
  • from-file config section to read a version from a file instead of the VCS.
  • POETRY_DYNAMIC_VERSIONING_DEBUG environment variable for some logging.
• Changed:
  • Updated Dunamai to 1.21.0+ for the latest features.

v1.2.0 (2023-12-02)

• Added:
  • initial-content-jinja option in tool.poetry-dynamic-versioning.files section.
• Fixed:
  • Line ending style was not preserved in some cases because of the default behavior of pathlib.Path.read_text. To avoid this, pathlib.Path.read_bytes is used instead now. (Contributed by nardi)

v1.1.1 (2023-10-27)

• Fixed:
  • Custom substitutions in pyproject.toml weren't cleaned up correctly. This was because the plugin would record the "original" content of the file after the version and enable fields had already been changed. Now, substitutions are reverted first before reverting version and enable.

v1.1.0 (2023-10-01)

• Added:
  • tool.poetry-dynamic-versioning.files config section. This allows you to create a file in a default state before applying substitutions to it. You can also leave the substitutions in place when the plugin deactivates.

v1.0.1 (2023-08-21)

• Fixed:
  • Compatibility with poetry-core 1.7.0, which removed the poetry.core.semver module.
  • The enable command now constrains the plugin version to >=1.0.0,<2.0.0 to protect against any potential API changes.

v1.0.0 (2023-08-18)

• Fixed:
  • Running poetry dynamic-versioning followed by poetry build would leave the plugin enabled in the sdist's pyproject.toml.

... (truncated)

Changelog

Sourced from poetry-dynamic-versioning's changelog.

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)

v1.3.0 (2024-04-29)

• Added:
  • pattern-prefix option to add a prefix to the version tag pattern.
  • ignore-untracked option to control the detection of dirty state.
  • from-file config section to read a version from a file instead of the VCS.
  • POETRY_DYNAMIC_VERSIONING_DEBUG environment variable for some logging.
• Changed:
  • Updated Dunamai to 1.21.0+ for the latest features.

v1.2.0 (2023-12-02)

• Added:
  • initial-content-jinja option in tool.poetry-dynamic-versioning.files section.
• Fixed:
  • Line ending style was not preserved in some cases because of the default behavior of pathlib.Path.read_text. To avoid this, pathlib.Path.read_bytes is used instead now. (Contributed by nardi)

v1.1.1 (2023-10-27)

• Fixed:
  • Custom substitutions in pyproject.toml weren't cleaned up correctly. This was because the plugin would record the "original" content of the file after the version and enable fields had already been changed. Now, substitutions are reverted first before reverting version and enable.

... (truncated)

Commits

• ae00d3a Release v1.4.0
• c4e2162 #180: Update changelog
• 5188507 Merge pull request #181 from edgarrmondragon/poetry-pep621
• fb39941 Remove 'version' from 'dynamic' list as needed
• 4a126ca Fix test pyproject updates
• 160e8a9 Add test case for 'poetry build'
• decb8b3 Fix test cleanup
• 41d454b Expect failure in PEP 621 mode without dynamic version requested
• 33e68b4 Fix test setup
• 978a9a1 Fix some unconditional references to tool.poetry
• 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)