-
Notifications
You must be signed in to change notification settings - Fork 560
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
SPECS/cni-plugins: update to v1.3.0 and set version while building #6396
Conversation
55383ee
to
5c54ee3
Compare
I finally managed to build package locally. Pushed a fix for setting the version. It builds and prints correctly now. |
Buddy Build Queued: 434883 |
Build passed |
Spec linting is failing because of other packages. Should I fix those as part of this PR? |
5c54ee3
to
af711fe
Compare
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.
Changes themselves look good but there is a merge conflict to resolve in the spec changelog
No, this PR can just focus on the cni-plugins change |
Refs microsoft#6339 Also move declarations around to satisfy linter. Signed-off-by: Mateusz Gozdek <mgozdek@microsoft.com>
af711fe
to
3f36671
Compare
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-static
subpackages, etc.) have had theirRelease
tag incremented../cgmanifest.json
,./toolkit/scripts/toolchain/cgmanifest.json
,.github/workflows/cgmanifest.json
)./SPECS/LICENSES-AND-NOTICES/data/licenses.json
,./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md
,./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON
)*.signatures.json
filessudo make go-tidy-all
andsudo make go-test-coverage
passSummary
What does the PR accomplish, why was it needed?
To address issues stated in #6339
Change Log
-v
Does this affect the toolchain?
YES/NO
NO
Associated issues
Test Methodology