ci(hotfix): update version detection format in workflow

[Aaron ("AJ") Steers (aaronsteers)]

Modify the version detection format in the workflow to include additional formatting options and comment out the tag trigger.

Summary by CodeRabbit

• Chores
  • Enhanced the automated versioning process with a more descriptive format incorporating unique run identifiers.
  • Adjusted error handling to log warnings instead of halting on version mismatches, ensuring smoother operations.
  • Streamlined configuration by removing an explicit version style setting in favor of default behavior.

[Aaron ("AJ") Steers (aaronsteers)]

Force-merging as hotfix to resolve format issue discovered after merging:

• CI: Implement automatic dynamic versioning for pre-releases #469

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The changes update the version detection and validation logic in the .github/workflows/pypi_publish.yml file. The Dunamai action now uses a custom format for version generation, and the workflow logs a warning (instead of failing) when there is a mismatch between the detected and input version. Additionally, the pyproject.toml file has been modified by removing the line specifying the "pep440" style within the [tool.poetry-dynamic-versioning] section, which may affect the dynamic versioning behavior.

Changes

File(s)	Change Summary
.github/workflows/pypi_publish.yml	Updated the Dunamai argument from --style pep440 to --format "{base}.post{distance}.dev${{ github.run_id }}" and modified error handling to log a warning instead of exiting on version mismatch.
pyproject.toml	Removed the style = "pep440" line from the [tool.poetry-dynamic-versioning] section, which may result in the default versioning style being applied.

Sequence Diagram(s)

sequenceDiagram
    participant Runner as GitHub Runner
    participant Dunamai as Dunamai Action
    participant Validator as Version Validator
    participant Publisher as Publishing Process

    Runner->>Dunamai: Execute version detection with custom format
    Dunamai-->>Runner: Return computed version
    Runner->>Validator: Validate version (computed vs input)
    alt Version Mismatch
        Validator-->>Runner: Log warning and use input version
    else Version Match
        Validator-->>Runner: Confirm versions match
    end
    Runner->>Publisher: Continue with publishing process

Loading

Possibly related PRs

• ci: add environment declaration for DockerhHub publish #78: Modifications to version detection and validation logic in the same workflow file. wdyt?
• fix: combined publish flow for CDK/SDM #77: Adjustments in the publishing workflow logic that align with these versioning changes. wdyt?
• CI: Implement automatic dynamic versioning for pre-releases #469: Enhancements using Dunamai for version detection and validation in the .github/workflows/pypi_publish.yml file, similar to the current updates. wdyt?

Suggested labels

bug

Suggested reviewers

• maxi297
• ChristoGrab

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 168c1ab and ddd491a.

📒 Files selected for processing (2)

• .github/workflows/pypi_publish.yml (2 hunks)
• pyproject.toml (0 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.