updating-upstream-refs

To update upstream package versions in a BuildStream project, you can manually bump versions in .bst files or use automated dependency tracking via `bst source track` and Renovate for git repositories and tarballs.

Tracking dependencies with BuildStream and Renovate involves configuring Renovate for PyPI, GitHub Releases, and Docker registries, while using `bst source track` to automatically update git_repo and remote sources.

To manually update a tarball source in BuildStream, you must download the new tarball, calculate its SHA256 checksum, and update both the version number and checksum fields directly in the corresponding .bst file.

Yes, Renovate works with PyPI, GitHub Releases, and Docker registries to automate build system updates, providing configured workflows that automatically track and bump upstream dependency versions without manual intervention.

You should manually bump a package version instead of using automated dependency tracking when handling specific tar or remote sources that require explicit SHA256 checksum verification, or when automated tools like Renovate fail to detect the upstream update.

Yes, you can configure Renovate to automate updates for git_repo sources in the Bluefin build system, which streamlines the process of keeping upstream references and package dependencies synchronized with their remote repositories.