Skip to content

Conversation

@tschaefer
Copy link
Owner

No description provided.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This pull request adds the ability to specify a custom Alloy version for deployment and updates, rather than always defaulting to the latest version. Users can now set a specific version (e.g., "v1.12.0") via the --alloy.version flag in both deploy and update commands.

Key Changes:

  • Refactored version fetching logic to support both "latest" and specific version strings
  • Added --alloy.version flag to deploy and update commands with "latest" as default
  • Updated download URL construction to handle versioned releases

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 8 comments.

Show a summary per file
File Description
internal/agent/update.go Extracted latest tag fetching into separate function and added version parameter support to update flow
internal/agent/deploy.go Modified download URL construction to handle both "latest" and specific version strings
internal/agent/agent.go Added version parameter to Deploy and Update public methods
cmd/agent/update.go Added --alloy.version flag and passed it to Update method
cmd/agent/deploy.go Added --alloy.version flag and passed it to Deploy method
internal/agent/agent_test.go Updated test calls to include "latest" version parameter

@tschaefer tschaefer force-pushed the feature/make-alloy-version-settable branch from 3c81f4c to 48e1008 Compare January 8, 2026 16:13
@tschaefer tschaefer marked this pull request as ready for review January 8, 2026 17:44
@tschaefer tschaefer merged commit f587d41 into main Jan 8, 2026
2 checks passed
@tschaefer tschaefer deleted the feature/make-alloy-version-settable branch January 8, 2026 17:48
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.

2 participants