Skip to content

Why does newer build produce 26.0 instead of 26.1? #7

@DienoX

Description

@DienoX

Why does the newer build produce 26.0 instead of 26.1?

Hi,

I noticed a difference between these two GitHub Actions runs:

The newer build produces version 26.0, while the older one resulted in 26.1.

Could you please explain what changed between these runs that caused the version to go down instead of up?

I’m trying to understand:

  • What is the main difference between these two builds?
  • Was there any change in versioning logic or configuration?
  • Is this downgrade intentional or a bug?

Thanks in advance for your help.

Best regards

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions