Skip to content

chore: add Renovate config with a 1-day minimum release age - #89

Merged
B4nan merged 3 commits into
masterfrom
chore/renovate-config
Aug 20, 2026
Merged

B4nan merged 3 commits into
masterfrom
chore/renovate-config

Conversation

@B4nan

@B4nan B4nan commented Aug 20, 2026

Copy link
Copy Markdown
Member

Sets up Renovate the same way as the other apify tooling repos (mirroring apify-client-js): weekday schedule, grouped and auto-merged patch/minor updates, lockfile maintenance, and semantic chore commits.

On top of the shared convention it enforces a minimum release age of 1 day at both levels:

  • Renovate: minimumReleaseAge: "1 day" globally (0 days for our own packages), so freshly published releases get a day of soak time before Renovate proposes them.
  • Yarn: npmMinimalAgeGate: 1d in .yarnrc.yml, so resolutions done by yarn itself respect the same gate. The option needs a newer yarn, so the vendored release is bumped 4.6.0 → 4.18.0 (lockfile diff is metadata-only, no dependency changes).

Both are a buffer against compromised releases, in the same spirit as the action SHA-pinning in #88, which Renovate will now also keep bumped.

Same setup as the other apify tooling repos (apify-client-js flavor):
weekday schedule, grouped auto-merged patch/minor updates, lockfile
maintenance, and minimumReleaseAge of 1 day as a supply-chain buffer
(0 days for our own packages). Renovate also keeps the SHA-pinned
GitHub Actions from #88 updated.
@B4nan
B4nan requested a review from barjin August 20, 2026 12:17
B4nan added 2 commits August 20, 2026 14:20
Adds npmMinimalAgeGate: 1d to .yarnrc.yml so the gate also applies to
resolutions done by yarn itself, not only to Renovate PRs. The option
needs a newer yarn, so the vendored release is bumped 4.6.0 -> 4.18.0
(lockfile diff is metadata-only: format version and the builtin
resolve-patch hash, no dependency changes).
The package manager's 4.18 node-modules hoisting surfaces the
@types/react@* (v19) copy nested under @docusaurus/types, which the
4.6 layout happened to mask, and the two React type trees break tsc.
Resolve everything to the project's ^18.3.3.

@barjin barjin left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I don't recall the reason why we still use yarn here - perhaps we could switch to pnpm? This package is sufficiently internal.

Approving nonetheless 👍

@B4nan
B4nan merged commit b17d297 into master Aug 20, 2026
3 checks passed
@B4nan

B4nan commented Aug 20, 2026

Copy link
Copy Markdown
Member Author

Yeah, maybe later, or never :) I guess we forgot about this one during the migration.

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.

3 participants