Go back to using .Os and .Arch in publisher step#748
Merged
Conversation
Contributor
🤖 GitHub commentsJust comment with:
|
v1v
reviewed
Feb 11, 2026
Member
v1v
left a comment
v1v
left a comment
There was a problem hiding this comment.
When you ran this, did it create two folders:
.aws-linux-amd64.aws-linux-arm64
Those are the folders used for running the Lambda publisher.
Member
Author
|
I do see the script running twice, once with |
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
2 participants
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.
Using
.Runtime.Goosand.Runtime.Goarchis wrong, as they come from the runtime, and therefore match the os/arch of the CI runner.I do get the proper environment set when I run this on a linux box.
I have added a
printenvnevertheles, as this used to fail withGOOSnot being set.