Skip to content

chore: add Renovate release-age gate and keep example algosdk in lockstep - #30

Merged
drichar merged 1 commit into
mainfrom
chore/renovate-algosdk-and-release-age
Oct 14, 2026
Merged

drichar merged 1 commit into
mainfrom
chore/renovate-algosdk-and-release-age

Conversation

@drichar

@drichar drichar commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Summary

Two changes to the Renovate config so the issues fixed manually in #24 don't come back:

  • minimumReleaseAge: "2 days": Renovate waits until a release is 2 days old before proposing it. chore(deps): Update all non-major dependencies #24 pulled in algosdk 3.9.0 about 5 hours after it was published, and the non-major group automerges, so new releases could otherwise reach main with no waiting period.
  • rangeStrategy: "bump" for algosdk: because of :preserveSemverRanges, Renovate bumped the SDK's pinned algosdk devDependency but left the examples at ^3.5.2. Two copies got installed, their types clashed, and examples/node-cli failed to build with TS2322. The rule bumps the examples' ranges along with the SDK's pinned version. It only matches dependencies and devDependencies, so the SDK's ^3.0.0 peer range is never widened or narrowed for consumers.

Testing

  • renovate-config-validator passes
  • prettier --check renovate.json passes

@drichar
drichar merged commit e93bd4e into main Oct 14, 2026
1 check passed
@drichar
drichar deleted the chore/renovate-algosdk-and-release-age branch October 14, 2026 21:17
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.

1 participant