<!-- Thank you for opening this feature request! You are helping make eksctl a better project :) In order to help us process this request faster, please provide as much detail as possible. Before creating a feature request, please search existing issues to see if this request has already been made. If there is a similar feature request please up-vote it and/or add your comments to it instead. For more information on how to contribute to eksctl, please refer to our contributing docs. https://github.com/eksctl-io/eksctl/blob/main/CONTRIBUTING.md#opening-issues --> ### What feature/behavior/change do you want? <!-- A clear and concise description of the change you would like to see in eksctl. Do not hesitate, when appropriate, to share the exact commands or API you would like, and/or to share a diagram (e.g.: asciiflow.com): "a picture is worth a thousand words". --> The pipeline should include an executable **outside** of the eksctl package that: * Imports eksctl * Initializes go.mod against an eksctl candidate * Builds and runs This need not be complicated, nor even connect to an actual EKS instance. This is an example. https://github.com/tendervittles/bad-eksctl ### Why do you want this feature? <!-- A clear and concise description of why you want this feature. What is it you are trying to accomplish? Include use-cases and any specific constraints you may have. --> I have hit https://github.com/eksctl-io/eksctl/issues/8090 and https://github.com/eksctl-io/eksctl/issues/8284 when trying to import eksctl. Both could have been easily detect before release by building an outside executable against this project.