Skip to content

Versioning: SpecFlow/Reqnroll packages are tied to specific xRetry version #297

@JoshKeegan

Description

@JoshKeegan

Noticed while reviewing the new Reqnroll xunit v3 plugin, but it's an existing issue copied from the current Reqnroll plugin. The nuspec targets a specific xRetry version, but we no longer release them all in-step. This is likely a hang-over from the old versioning where all plugins got released every time.

Problem is: we might release v1.0.0 of xRetry.v3, and v1.0.0 of xRetry.Reqnroll.v3, and then later release a fix for xRetry.v3 as v1.0.1. Reqnroll users would be prevented from upgrading xRetry.v3, and getting the fix. The nuspec constraints should probably be loosened to allow upgrades within the same major version.

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