Skip to content

Newer version detection is incorrect #232

Closed

Description

@leggetter
Image

It could be that the beta tag confused things a little bit, or it could be that it treats 1.9 as newer than 1.10, which is obviously wrong.

Activity

  1. leggetter commented on Mar 16, 2026

    @leggetter
    CollaboratorAuthor

    Could you provide more details to help reproduce this issue? Specifically:

    1. What are the exact version numbers being compared (current vs detected newer version)?
    2. What is the expected behavior vs actual behavior?
    3. Can you share the relevant code or configuration where this version detection occurs?
    4. Are you able to reproduce this consistently?

    The screenshot helps show the issue exists, but we need more technical details to implement a proper fix.

  2. leggetter commented on Mar 16, 2026

    @leggetter
    CollaboratorAuthor

    1.10.0-beta.4 compared to v1.9.1. It's saying v1.9.1 is newer than 1.10.0-beta.4.

    This is wrong because from 1.10 down to 1.9 is a downgrade. Maybe there's some logic in there that kind of goes okay. It's not the newest non-beta version.

    In that case, they should just not be prompted now. If they're on a beta and there's a newer non-beta, they should be prompted. If they're on a beta and there's a newer beta, they should be prompted. If they're on GA and there's a newer beta, they shouldn't be prompted to upgrade from a GA to a beta.

  3. github-actions commented on Mar 16, 2026

    @github-actions
    Contributor

    The auto-implement run could not complete: verification failed after 3 attempts. See the workflow run for logs. You can address the failure and re-trigger by adding a comment or re-applying the label.

  4. github-actions commented on Mar 16, 2026

    @github-actions
    Contributor

    The auto-implement run could not complete: verification failed after 3 attempts. See the workflow run for logs. You can address the failure and re-trigger by adding a comment or re-applying the label.

  5. github-actions commented on Mar 16, 2026

    @github-actions
    Contributor

    The auto-implement run could not complete: verification failed after 3 attempts. See the workflow run for logs. You can address the failure and re-trigger by adding a comment or re-applying the label.

  6. github-actions commented on Mar 17, 2026

    @github-actions
    Contributor

    The auto-implement run could not complete: verification failed after 3 attempts. See the workflow run for logs. You can address the failure and re-trigger by adding a comment or re-applying the label.

  7. leggetter commented on Mar 17, 2026

    @leggetter
    CollaboratorAuthor

    Fixed in #250

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions