Make version number dynamic in integration tests
#6017
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Every time we release a new version, the integration tests start failing. This
is because we have a CLI test where we look at the output of the
tailwindcss --helpoutput.This output contains a version number, that will be out of date when we release a new version.
This PR fixes that by making the version dynamic based on the
package.jsonversion value. This should be safe to do because the goal of the tests is
ensuring that the CLI help output is consistent, not so much the version
number. BUT it is still important that the version is in sync. This will ensure
it is always in sync.
The text was updated successfully, but these errors were encountered: