Replies: 2 comments 3 replies
-
oh darn. This might be because when you specify the action at v1.12.0 it goes to the code at that point and determines which package to pull. See here the v1.12.0 of the code that specifies the package: https://github.com/github/evergreen/blob/v1.12.0/action.yml#L7 You can see it just goes to the registry and pulls the v1 tag of the container. We will need some automation to get that updated to the specific container version every time a release occurs. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Here's a workaround that worked for me:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am a bit confused and looking for some clarification.
I target specifically a minor version in my setup, like this:
and I noticed that it still always end up puling the latest major version (from a run log):
But in the registry I do see that there are tags with the minor versions, for example https://github.com/github/evergreen/pkgs/container/evergreen/260302251?tag=v1.12.0
So what should I do to pin evergreen to a specific minor v?
cc @zkoppert
Beta Was this translation helpful? Give feedback.
All reactions