[master] Auto-update dependencies (#248)

Produced via:
  `./hack/update-deps.sh --upgrade && ./hack/update-codegen.sh`
/assign n3wscott vagababov
/cc n3wscott vagababov

Gopkg.lock

@@ -966,7 +966,7 @@
 
 [[projects]]
   branch = "master"
-  digest = "1:80c0e243552e01cdec518680967f72e6a435c4277b97b3ebf2e08f6590a389e7"
+  digest = "1:848ae8fad4b88bbe3e0944f2a68052e14c4e1bb345d7b32f9d0a0ffdc2c90b46"
   name = "knative.dev/pkg"
   packages = [
     "apis",
@@ -986,7 +986,7 @@
     "reconciler",
   ]
   pruneopts = "T"
-  revision = "9147309d53665ac87d8a5a17dabdbe3e24c97d13"
+  revision = "4e57475bc87c1aba3e7fcc0207b593dc7186eb83"
 
 [[projects]]
   branch = "master"
@@ -997,7 +997,7 @@
     "tools/dep-collector",
   ]
   pruneopts = "UT"
-  revision = "5e04d955cdb9a460b5d3f2a699bddcab22c8af94"
+  revision = "74b24ca44778c3a69ecc193250cdddb5d0e64b88"
 
 [[projects]]
   digest = "1:8730e0150dfb2b7e173890c8b9868e7a273082ef8e39f4940e3506a481cf895c"

vendor/knative.dev/pkg/RELEASING.md

@@ -6,11 +6,11 @@ release, but likely this should happen incrementally over each milestone.
 
 ## Release Process.
 
-### Step #1: Monday the week prior to each release.
+### Step #1: 7 days prior to each release.
 
-On Monday of the week prior to the Knative release, each of the downstream
+7 days prior to the Knative release, each of the downstream repositories should
-repositories should stage a `[WIP]` Pull Request that advances the knative/pkg
+stage a `[WIP]` Pull Request that advances the knative/pkg dependency to the
-dependency to the latest commit.
+latest commit.
 
 At present, these downstream repositories include:
 
@@ -47,9 +47,26 @@ process repeats until knative/pkg can be cleanly updated without any changes.
 ### Step #2: Friday the week prior to each release.
 
 A release branch is snapped on knative/pkg with the form `release-0.X` where `X`
-reflects the forthcoming Knative release. The commit at which this branch is
+reflects the forthcoming Knative release.
-snapped will be the version that has been staged into `[WIP]` PRs in every
+
-repository.
+Any releaseable components inside of `knative/pkg` also need to be set to their
+release branch to avoid trivial point releases during the next release. At the
+moment we have the following Knative dependecies inside of `pkg`:
+
+- knative.dev/test-infra
+
+Update these to point to a release branch for the current release and update the
+toml entry on the `knative.dev/pkg:release-0.X` branch, like:
+
+```toml
+[[constraint]]
+  name = "knative.dev/test-infra"
+  branch = "release-0.14"
+```
+
+After this updated in the `pkg` release branch, apply this commit at which this
+branch is snapped will be the version that has been staged into `[WIP]` PRs in
+every repository.
 
 These staging PRs are then updated to:
 
@@ -62,6 +79,9 @@ These staging PRs are then updated to:
 
 The `[WIP]` is removed, and the PRs are reviewed and merged.
 
+> Note: a simple tool has been written to help with the
+> [toml editing](https://github.com/n3wscott/tomles).
+
 ## Backporting Fixes
 
 If a problem is found in knative/pkg in an older release and a fix must be

vendor/knative.dev/pkg/controller/controller.go

@@ -306,6 +306,16 @@ func (c *Impl) EnqueueLabelOfClusterScopedResource(nameLabel string) func(obj in
 	}
 }
 
+// EnqueueNamespaceOf takes a resource, and enqueues the Namespace to which it belongs.
+func (c *Impl) EnqueueNamespaceOf(obj interface{}) {
+	object, err := kmeta.DeletionHandlingAccessor(obj)
+	if err != nil {
+		c.logger.Errorw("EnqueueNamespaceOf", zap.Error(err))
+		return
+	}
+	c.EnqueueKey(types.NamespacedName{Name: object.GetNamespace()})
+}
+
 // EnqueueKey takes a namespace/name string and puts it onto the work queue.
 func (c *Impl) EnqueueKey(key types.NamespacedName) {
 	c.WorkQueue.Add(key)