Skip to content

chore(ci): Trigger renovate after SDK release#266

Merged
kodiakhq[bot] merged 1 commit intocloudquery:mainfrom
erezrokah:chore/trigger_renovate
Oct 9, 2022
Merged

chore(ci): Trigger renovate after SDK release#266
kodiakhq[bot] merged 1 commit intocloudquery:mainfrom
erezrokah:chore/trigger_renovate

Conversation

@erezrokah
Copy link
Copy Markdown
Member

@erezrokah erezrokah commented Oct 9, 2022

Summary

This is a small optimization to how we do SDK updates in the monorepo. At the moment renovate runs every 15 minutes to handle dependencies updates. We run it every 15 minutes to ensure speedy updates to the SDK.
With this PR we'll run it immediately after the SDK has been released.
This should also allow us to save some build minutes by reducing the renovate schedule to 1 hour for example


Use the following steps to ensure your PR is ready to be reviewed

  • Read the contribution guidelines 🧑‍🎓
  • Run go fmt to format your code 🖊
  • Lint your changes via golangci-lint run 🚨 (install golangci-lint here)
  • Update or add tests 🧪
  • Ensure the status checks below are successful ✅

Copy link
Copy Markdown
Contributor

@yevgenypats yevgenypats left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! BTW - Im curious now if we can remove the .github repository and have the renovate workflows directly in cloudquery/cloudquery ?

@kodiakhq kodiakhq bot merged commit ad9ba4e into cloudquery:main Oct 9, 2022
@erezrokah
Copy link
Copy Markdown
Member Author

erezrokah commented Oct 9, 2022

Im curious now if we can remove the .github repository and have the renovate workflows directly in cloudquery/cloudquery ?

Yeah we could. We still have the renovate presets there though https://github.com/cloudquery/.github/tree/45b1684b59eb6b23f79903e288858020ed02680f/.github (both the SDK and CloudQuery repos uses those), and some generic issue/pr/security/code of conduct templates, so it makes sense to still keep that repo for the latter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants