Skip to content

chore: Update CI with new actions and change renovate schedule #25

New issue

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

Merged
merged 5 commits into from
Sep 22, 2022

Conversation

jimmycallin
Copy link
Contributor

@jimmycallin jimmycallin commented Sep 22, 2022

  • I have added automatic tests where applicable
  • The PR title is suitable as a release note
  • The PR contains a description of what has been changed
  • The description contains manual test instructions

Changes

  • The Renovate schedule was a bit too noisy, so changing it to running once every 3 months. It should be often enough to keep the library up to date, while rare enough to not become a chore.
  • Added new CI steps.

Test

Make sure CI is green.

@jimmycallin jimmycallin requested a review from a team as a code owner September 22, 2022 15:09
renovate.json Outdated
],
"rangeStrategy": "update-lockfile",
"schedule": [
"every 3 months on the first day of the month"
Copy link
Contributor

Choose a reason for hiding this comment

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

I agree with the noise issue. Especially in this repository, where (At least to me) testing if anything breaks is a hassle. But my vote would be on seeing if once a month would work. I could even take the opportunity to take a more active role in the approval pipeline for renovate.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it is done!

@jimmycallin jimmycallin merged commit c15f6de into main Sep 22, 2022
@jimmycallin jimmycallin deleted the chore/renovate-schedule branch September 22, 2022 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants