Services, support and updates

Software updates

Have Yavaren update a repository's dependencies, runtime or framework, or fix security advisories, as draft pull requests.

Open Updates to have Yavaren update your software for you. Each update arrives as a draft pull request: your team reviews and merges it; Yavaren never does.

Asking for an update

You need member access. Pick the project and repository, and what to update:

• Dependencies, how far: patch (bug-fix releases only), minor (the default: no breaking version) or major (the newest releases; code is adapted to breaking changes).
• Runtime or framework: name it and the version to move to (for example node and 22).
• Security advisories only: just the packages an advisory names, to the smallest version that fixes it.

Tulaian works out what is outdated with the repository's own package manager (for pip and Gradle projects, by asking the public registries PyPI and Maven Central from your runner; never from an installation with no internet connection), makes the update, runs your build and tests and the quality checks, and opens the draft pull request. It lists every package with its old and new version and a link to its release notes, and shows the quality scorecard.

Repeating updates

An admin can have a repository updated every few weeks. Each run is started once; a run that fails is not started again by itself. Switch a repeating update off at any time. With Skip while open, a run is skipped (and listed as Skipped, with the reason) while the previous update pull request of that schedule is still open.

What you see

The page lists the open update pull requests, every update asked for and how it went (draft opened, nothing to update, skipped, or failed and why) and what became of its pull request (open, merged, or closed without merging, as your repository host reports it), and the repeating updates.