Closed petcuvio closed 10 months ago
You can pin the CLI using version
setting, as shown in the README.
Not sure the versioning strategy can be more 'clear' than latest
being the latest release. Major releases with breaking changes are rare (2 in ~5 years).
Busted 😄
Did not read the documentation thoroughly. Testing now ... will of course close the issue.
@jdkato thanks for the quick reply.
Hello everyone,
I've encountered a significant issue with the
vale-action
due tovale cli
where thelatest
tag now points to3.0.0
. This version introduces configuration changes that are not backwards compatible, causing a disruption in our workflows.Description of the Issue
The problem started after the
latest
tag ofvale cli
was updated to3.0.0
. Our existing configurations are not compatible with this new version, leading to workflow failures. Here's an example of the issue:To mitigate this, I attempted to pin the action to a specific commit (
c99f2dfd2aeaedb3d4bb16f385841830b9164d31
), but it appears that the action still defaults to using thelatest
version ofvale cli
, which doesn't resolve our problem:Proposed Solution
To ensure stability and prevent such disruptions in future releases, I propose implementing either of the following:
vale cli
that does not automatically update to the latest.latest
tag, allowing users to prepare for backward-incompatible changes.Classification
I am not sure if this should be classified as a :red_circle:
BUG
or a :large_blue_circle:FEATURE
request, but I believe addressing this issue is crucial for maintaining stable workflows.Thank you for your attention to this matter. Looking forward to your thoughts and suggestions.