We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
During the release of Kedro 0.19.0 we got blocked because there was no compatible tag of kedro-starters and kedro-telemetry:
#3411 (comment)
At the moment, there is an automation that tags a kedro-starters release after the corresponding kedro release is up, introduced in #2889 https://github.com/kedro-org/kedro/blob/fb385ef/.github/workflows/release-starters.yml
For kedro-telemetry, releases are pinned to specific major versions.
Maybe we'd need to reconsider this process. Even if major releases only happen from time to time, it's less than ideal.
Other alternatives could be explored.
The text was updated successfully, but these errors were encountered:
There's no action from this, in practice we are already doing it. Closing.
Sorry, something went wrong.
No branches or pull requests
During the release of Kedro 0.19.0 we got blocked because there was no compatible tag of kedro-starters and kedro-telemetry:
#3411 (comment)
At the moment, there is an automation that tags a kedro-starters release after the corresponding kedro release is up, introduced in #2889 https://github.com/kedro-org/kedro/blob/fb385ef/.github/workflows/release-starters.yml
For kedro-telemetry, releases are pinned to specific major versions.
Maybe we'd need to reconsider this process. Even if major releases only happen from time to time, it's less than ideal.
Other alternatives could be explored.
The text was updated successfully, but these errors were encountered: