ci: automate Alloy version updates - #187
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
alloy-rs/alloyGitHub release every day and on manual dispatchWhy
The documented Alloy version currently requires a manual release-bump PR such as #186. Automating that maintenance keeps the version selector, installation snippets, and agent discovery metadata aligned with published releases.
Impact
After this lands, new Alloy releases will produce a ready-for-review documentation PR from
automation/update-alloy-version. This is a follow-up to #186 and should land after it to avoid creating a duplicate initial 2.4.1 bump.