-
Notifications
You must be signed in to change notification settings - Fork 264
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
kn v0.16.0 release prep #922
kn v0.16.0 release prep #922
Conversation
Fixes knative#918 Use DeprecatedInjectionAnnotation, i.e. "knative-eventing-injection" for reconciling broker via namespace labeling and trigger annotations. From eventing v0.16.0 release, this key is changed to "eventing.knative.dev/injection" however, older eventing installation wont recognize it. So we continue using the deprecated key until the sugar-controller would support reconciling on either keys.
We've been showing 'v1alpha1' in kn version while we actually vendor and refer v1beta1 for eventing.knative.dev
@@ -0,0 +1,257 @@ | |||
package lru |
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.
this file looks bogus
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.
As it turns out, according to google/go-licenses#28 its because that for "Reciprocal" licenses the whole source code is copied (regardless whether it has been changed or not).
@@ -0,0 +1,177 @@ | |||
package simplelru |
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.
same ... I don't think the mechanism of picking up those licenses is bullet proof
the new error message for incorrect concurrency-target value contains "should be at least 0.01"
/retest |
@navid I think we have a real error in the traffic split tests. I.e. that some condition doesn't eventually happens. |
@rhuss : broker injection ones instead, while the service options one is flake (
This is failing against v0.16.0 install of eventing,I will check further. |
- reuse knative_setup util from common lib for latest-release CI setup
38ef5fe
to
8fe2114
Compare
third_party/VENDOR-LICENSE/github.com/hashicorp/hcl/hcl/scanner/scanner.go
Show resolved
Hide resolved
third_party/VENDOR-LICENSE/github.com/hashicorp/hcl/json/scanner/scanner.go
Show resolved
Hide resolved
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.
Thanks for including licenses in one place. LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: maximilien, navidshaikh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thanks ! /lgtm |
Description
kn v0.16.0 release prep
Changes
Vendor v0.16.0 eventing and serving
Update unit test for invalid concurrency target value
Commit the LICENSES generated by hack/update-deps.sh
Spare third_party dir from license check in hack/build.sh
Update eventing and serving version for 'kn version'
Use DeprecatedInjectionAnnotation key for backward compatibility
Fixes Switch to DeprecatedInjectionAnnotation from InjectionAnnotation for backward compatibility #918
Use DeprecatedInjectionAnnotation, i.e. "knative-eventing-injection"
for reconciling broker via namespace labeling and trigger annotations.
From eventing v0.16.0 release, this key is changed to "eventing.knative.dev/injection"
however, older eventing installation wont recognize it. So we continue
using the deprecated key until the sugar-controller would support reconciling
on either keys.
Fix(kn version): Display eventing.knative.dev at v1beta1 version
We've been showing 'v1alpha1' in kn version while we actually
vendor and refer v1beta1 for eventing.knative.dev
chore(e2e): Run tests against serving/eventing v0.16.0 release
Update test for concurrency-target to expect new error message
the new error message for incorrect concurrency-target value contains "should be at least 0.01"