You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we experience issues with upgrading crystal version due to incompatible versions of ameba and crystal.
And even through Ameba is mentioned in dependencies of testsuite, it isn't being used in any way for CI or otherwise.
Proposal is to remove Ameba from project dependencies, and then, in future issues, update crystal version and later, add Ameba to CI via building it from source.
No other projects under testsuite use Ameba, it should be safe to only remove it from shard.yml and shard.lock here.
The text was updated successfully, but these errors were encountered:
Ameba is a linting tool, which isn't being used in our CI
pipelines, and causes complications with crystal version update.
Ameba dependency should be removed from cnf-testcatalog shards
and usage guidelines should point to more independent usage via
installing the linter from source.
Refs: cnti-testcatalog#2157
Signed-off-by: Konstantin Yarovoy <[email protected]>
* ameba: Remove ameba from shard dependencies
Ameba is a linting tool, which isn't being used in our CI
pipelines, and causes complications with crystal version update.
Ameba dependency should be removed from cnf-testcatalog shards
and usage guidelines should point to more independent usage via
installing the linter from source.
Refs: #2157
Signed-off-by: Konstantin Yarovoy <[email protected]>
* Update USAGE.md
Signed-off-by: Martin Matyas <[email protected]>
---------
Signed-off-by: Konstantin Yarovoy <[email protected]>
Signed-off-by: Martin Matyas <[email protected]>
Co-authored-by: Martin Matyas <[email protected]>
Ameba is a crystal-lang static linting tool, which can be ran in different ways. https://github.com/crystal-ameba/ameba
Currently we experience issues with upgrading crystal version due to incompatible versions of ameba and crystal.
And even through Ameba is mentioned in dependencies of testsuite, it isn't being used in any way for CI or otherwise.
Proposal is to remove Ameba from project dependencies, and then, in future issues, update crystal version and later, add Ameba to CI via building it from source.
No other projects under testsuite use Ameba, it should be safe to only remove it from shard.yml and shard.lock here.
The text was updated successfully, but these errors were encountered: