Skip to content

Conversation

@adaam2
Copy link
Member

@adaam2 adaam2 commented Oct 30, 2025

image (1)

The CLI confusingly displays two conflicting messages - this is because in the logic for displaying the message "Running with latest Speakeasy version" which is based on looking at the workflow.yaml speakeasyVersion: latest value, we do not actually check that we are on latest before rendering it (you can see from the subsequent screenshot that we do eventually autoupgrade)

@adaam2 adaam2 requested a review from ThomasRooney October 30, 2025 11:40
cmd/root.go Outdated
wf, _, _ := utils.GetWorkflow()

// If a workflow file is present and specifies that the speakeasyVersion is "latest", don't display update notifications as it will be automatically updated when the command is run.
if wf != nil && wf.SpeakeasyVersion.String() == "latest" {
Copy link
Member

Choose a reason for hiding this comment

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

We'd want to render the update available when a workflow file is present but when we're (for instance) running any non-workflow command? I.e. I think it's only workflow run which has weird output

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah fair play - it's only run that does the auto upgrade

Copy link
Member Author

Choose a reason for hiding this comment

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

That's fixed up now

Copy link
Member Author

Choose a reason for hiding this comment

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

@ThomasRooney bump on the review here ☝🏻

Think my scoping down is the right solution

Copy link
Member

@ThomasRooney ThomasRooney left a comment

Choose a reason for hiding this comment

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

need to scope the change more IMO

@adaam2 adaam2 requested a review from ThomasRooney October 30, 2025 15:42
@adaam2 adaam2 force-pushed the fix/update-message branch from c8d293f to b0808a0 Compare November 11, 2025 12:57
@adaam2 adaam2 merged commit 0f5bdf2 into main Nov 11, 2025
7 of 8 checks passed
@adaam2 adaam2 deleted the fix/update-message branch November 11, 2025 16:18
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.

6 participants