chore: bump ignition-devs/copier-templates to 0.4.27

[cesarcoatl]

Summary by Sourcery

Update CI and publish workflows to use pinned v7 coatl-dev reusable workflows and actions, and refresh Copier template metadata.

Build:

• Reorder and retain Commitizen pre-commit hooks without changing their configuration.

CI:

• Pin pre-commit, pylint, tox, and tox-docker reusable workflows and related GitHub actions to specific v7 SHAs in CI.
• Restrict tox-package and tox-stubs jobs in the publish workflow to run only on pull requests and use pinned v7 SHAs.

Chores:

• Bump Copier template reference from 0.4.25 to 0.4.27 in Copier answers metadata.

[sourcery-ai]

Reviewer's Guide

Updates GitHub Actions workflows to use pinned SHAs for v7.0.0 of shared coatl-dev workflows/actions and newer v6.x versions of official actions, adjusts publish workflow job conditions, reorders (but functionally preserves) Commitizen pre-commit hooks, and bumps the Copier template reference from 0.4.25 to 0.4.27.

Flow diagram for updated publish workflow job conditions in GitHub Actions

flowchart LR
    github_event[GitHub event]

    subgraph publish_workflow[.github/workflows/publish.yml]
      direction LR
      tox_package[Tox package tests]
      tox_stubs[Tox stubs tests]
      pypi_publish_package[PyPI upload package]
      pypi_publish_stubs[PyPI upload stubs]
    end

    github_event --> tox_package
    github_event --> tox_stubs

    tox_package --> pypi_publish_package
    tox_stubs --> pypi_publish_stubs

    %% New behavior: tox jobs only run for pull_request events
    tox_package:::prOnly
    tox_stubs:::prOnly

    classDef prOnly fill:#eef,stroke:#88f,stroke-width:1px;

Loading

File-Level Changes

Change	Details	Files
Update CI workflows to pin shared coatl-dev reusable workflows and GitHub Actions to newer versions.	Bump pre-commit reusable workflow from version v6 to SHA for coatl-dev/workflows v7.0.0. Bump pylint reusable workflow from version v6 to SHA for coatl-dev/workflows v7.0.0. Bump tox-docker and tox reusable workflows in CI from version v6 to SHA for coatl-dev/workflows v7.0.0. Pin actions/checkout to SHA corresponding to v6.0.3. Pin actions/cache to SHA corresponding to v5.0.5. Update coatl-dev/actions/setup-jython from version v5 to SHA for v7.0.0.	.github/workflows/ci.yml
Align publish workflow with updated reusable workflows and add pull_request conditions to test jobs.	Add if: ${{ github.event_name == 'pull_request' }} condition to tox-package and tox-stubs jobs in publish workflow. Update tox-docker and tox reusable workflows in publish workflow from version v6 to SHA for coatl-dev/workflows v7.0.0. Update pypi-upload reusable workflow references from version v6 to SHA for coatl-dev/workflows v7.0.0.	.github/workflows/publish.yml
Reorder Commitizen pre-commit hooks block while keeping configuration the same.	Move commitizen repo block to the end of the repos list, after the local pylint hook block, without changing its configuration.	.pre-commit-config.yaml
Bump Copier template source revision to the latest template version.	Update _commit from 0.4.25 to 0.4.27 in Copier answers file to reflect the template version used to generate the project.	.copier-answers.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• In .github/workflows/publish.yml, adding if: ${{ github.event_name == 'pull_request' }} to the tox-package and tox-stubs jobs effectively disables these checks for tag/release events; confirm this aligns with your intended publish flow since it may prevent running tox before publishing to PyPI.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In `.github/workflows/publish.yml`, adding `if: ${{ github.event_name == 'pull_request' }}` to the `tox-package` and `tox-stubs` jobs effectively disables these checks for tag/release events; confirm this aligns with your intended publish flow since it may prevent running tox before publishing to PyPI.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}