Skip to content

Conversation

bastelfreak
Copy link
Member

With thor 1.3.1 we've two failing tests:

Failing Scenarios:
cucumber features/execute.feature:36 # Scenario: Show fail-fast default value in help
cucumber features/execute.feature:44 # Scenario: Override fail-fast default value using config file

as a workaround to get CI green again we'r pinning to 1.3.0. I think the bug is fixed in rails/thor#878 but not yet released.

With thor 1.3.1 we've two failing tests:

```
Failing Scenarios:
cucumber features/execute.feature:36 # Scenario: Show fail-fast default value in help
cucumber features/execute.feature:44 # Scenario: Override fail-fast default value using config file
```

as a workaround to get CI green again we'r pinning to 1.3.0. I think the
bug is fixed in rails/thor#878 but not yet
released.
spec.add_runtime_dependency 'octokit', '>=4', '<9'
spec.add_runtime_dependency 'puppet-blacksmith', '>= 3.0', '< 8'
spec.add_runtime_dependency 'thor'
spec.add_runtime_dependency 'thor', '1.3.0'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should it have pinned to NOT 1.3.0?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's correct? 1.3.1 has a regression and rails/thor#878 contains a potential fix.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I meant to pin to != 1.3.1. I shouldn't send comments as I'm changing trains using the mobile app. Never ends well

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah ok. I considered that, but I don't know if the fix will be in 1.3.2 or later. So I think the safer way is pinning to 1.3.0 and dependabot will inform us for new releases.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason I mention it is because dependabot also informed us about 1.3.1, but yes, this stuff is always annoying

@bastelfreak bastelfreak deleted the thor branch May 17, 2024 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants