New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/1.3] Pin libseccomp to 2.3.3 for GH Actions release.yml #4352
Conversation
Going to verify this in my "actions playground" before we commit |
Build succeeded.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Assuming the playgrounds thing works :) |
Use the same pinning we were using in Travis CI to not force dependencies on the newer libseccomp 2.4.x in our binaries. Signed-off-by: Phil Estes <estesp@linux.vnet.ibm.com>
95bff1e
to
7013f1f
Compare
It is now; forgot the working directory the first commit. Second time's a charm; actions release worked and binary is linked to 2.3.3 libseccomp. |
Build succeeded.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Use the same pinning we were using in Travis CI to not force
dependencies on the newer libseccomp 2.4.x in our binaries.
Signed-off-by: Phil Estes estesp@linux.vnet.ibm.com
Fixes: #4349