upgrade to latest dependencies (#434)

bumping knative.dev/hack f99a255...9b73a25:
  > 9b73a25 Drop unnecessary occurrences of master (# 53)
bumping knative.dev/pkg 737401c...0f8d8de:
  > 0f8d8de Update common github actions (# 2051)
  > 185e333 Run downstream action on master branch too (# 2049)

Signed-off-by: Knative Automation <automation@knative.team>

go.mod

@@ -17,6 +17,6 @@ require (
 	k8s.io/client-go v0.19.7
 	k8s.io/code-generator v0.19.7
 	k8s.io/kube-openapi v0.0.0-20200805222855-6aeccd4b50c6
-	knative.dev/hack v0.0.0-20210305150220-f99a25560134
-	knative.dev/pkg v0.0.0-20210308052421-737401c38b22
+	knative.dev/hack v0.0.0-20210309141825-9b73a256fd9a
+	knative.dev/pkg v0.0.0-20210309024624-0f8d8de5949d
 )

go.sum

@@ -1188,8 +1188,10 @@ k8s.io/utils v0.0.0-20200729134348-d5654de09c73 h1:uJmqzgNWG7XyClnU/mLPBWwfKKF1K
 k8s.io/utils v0.0.0-20200729134348-d5654de09c73/go.mod h1:jPW/WVKK9YHAvNhRxK0md/EJ228hCsBRufyofKtW8HA=
 knative.dev/hack v0.0.0-20210305150220-f99a25560134 h1:lUllAp28TkevQIgWrsjow8ZLnXJy3AraRzGFm/ffD2c=
 knative.dev/hack v0.0.0-20210305150220-f99a25560134/go.mod h1:PHt8x8yX5Z9pPquBEfIj0X66f8iWkWfR0S/sarACJrI=
-knative.dev/pkg v0.0.0-20210308052421-737401c38b22 h1:f3IFaya7jysL+2oUJkPADTUhUn12R8AY3n6kWsgzp4w=
-knative.dev/pkg v0.0.0-20210308052421-737401c38b22/go.mod h1:fP690UCcs5x+qQVhjJxNcm97OWIiUdFC1dqbD3Gsp64=
+knative.dev/hack v0.0.0-20210309141825-9b73a256fd9a h1:0UGKyvFzY1Czu0lP9+0IrJhwtKe2oNLI2GYa7MIQ5c0=
+knative.dev/hack v0.0.0-20210309141825-9b73a256fd9a/go.mod h1:PHt8x8yX5Z9pPquBEfIj0X66f8iWkWfR0S/sarACJrI=
+knative.dev/pkg v0.0.0-20210309024624-0f8d8de5949d h1:2Uc3qyLRLIYOqJrGGKFkJc69X+cxlhoH3jk7p4b4KFM=
+knative.dev/pkg v0.0.0-20210309024624-0f8d8de5949d/go.mod h1:fP690UCcs5x+qQVhjJxNcm97OWIiUdFC1dqbD3Gsp64=
 pgregory.net/rapid v0.3.3/go.mod h1:UYpPVyjFHzYBGHIxLFoupi8vwk6rXNzRY9OMvVxFIOU=
 rsc.io/binaryregexp v0.2.0/go.mod h1:qTv7/COck+e2FymRvadv62gMdZztPaShugOCi3I+8D8=
 rsc.io/quote/v3 v3.1.0/go.mod h1:yEA65RcK8LyAZtP9Kv3t0HmxON59tX3rD+tICJqUlj0=

vendor/knative.dev/hack/README.md

@@ -281,7 +281,7 @@ This is a helper script for Knative release scripts. To use it:
    - `RELEASE_VERSION`: contains the release version if `--version` was passed.
      This also overrides the value of the `TAG` variable as `v<version>`.
    - `RELEASE_BRANCH`: contains the release branch if `--branch` was passed.
-     Otherwise it's empty and `master` HEAD will be considered the release
+     Otherwise it's empty and `main` HEAD will be considered the release
      branch.
    - `RELEASE_NOTES`: contains the filename with the release notes if
      `--release-notes` was passed. The release notes is a simple markdown file.

vendor/knative.dev/hack/library.sh

@@ -787,18 +787,18 @@ function shellcheck_new_files() {
 function latest_version() {
   # This function works "best effort" and works on Prow but not necessarily locally.
   # The problem is finding the latest release. If a release occurs on the same commit which
-  # was branched from master, then the tag will be an ancestor to any commit derived from master.
+  # was branched from main, then the tag will be an ancestor to any commit derived from main.
   # That was the original logic. Additionally in a release branch, the tag is always an ancestor.
-  # However, if the release commit ends up not the first commit from master, then the tag is not
-  # an ancestor of master, so we can't use `git describe` to find the most recent versioned tag. So
+  # However, if the release commit ends up not the first commit from main, then the tag is not
+  # an ancestor of main, so we can't use `git describe` to find the most recent versioned tag. So
   # we just sort all the tags and find the newest versioned one.
-  # But when running locally, we cannot(?) know if the current branch is a fork of master or a fork
+  # But when running locally, we cannot(?) know if the current branch is a fork of main or a fork
   # of a release branch. That's where this function will malfunction when the last release did not
   # occur on the first commit -- it will try to run the upgrade tests from an older version instead
   # of the most recent release.
   # Workarounds include:
   # Tag the first commit of the release branch. Say release-0.75 released v0.75.0 from the second commit
-  # Then tag the first commit in common between master and release-0.75 with `v0.75`.
+  # Then tag the first commit in common between main and release-0.75 with `v0.75`.
   # Always name your local fork master or main.
   if [ $(current_branch) = "master" ] || [ $(current_branch) = "main" ]; then
     # For main branch, simply use git tag without major version, this will work even

vendor/knative.dev/hack/microbenchmarks.sh

@@ -32,11 +32,11 @@ function microbenchmarks_run() {
   go test -bench=. -benchtime=$BENCH_RUN_TIME -count=$BENCH_RUN_COUNT -benchmem -run="^$" -v ./...   >> "$OUTPUT_FILE" || exit
 }
 
-# To run microbenchmarks on your machine and compare your revision with upstream/master:
+# To run microbenchmarks on your machine and compare your revision with upstream/main:
 #
 # git fetch upstream
 # source microbenchmarks.sh
-# microbenchmarks_run_and_compare upstream/master
+# microbenchmarks_run_and_compare upstream/main
 #
 # NOTE: Hypothetically we should run these microbenchmarks on a machine running only a kernel and a shell,
 # but this might be sometimes hard to achieve unless you have a spare computer to play with.

vendor/modules.txt

@@ -655,10 +655,10 @@ k8s.io/kube-openapi/pkg/util/sets
 k8s.io/utils/buffer
 k8s.io/utils/integer
 k8s.io/utils/trace
-# knative.dev/hack v0.0.0-20210305150220-f99a25560134
+# knative.dev/hack v0.0.0-20210309141825-9b73a256fd9a
 ## explicit
 knative.dev/hack
-# knative.dev/pkg v0.0.0-20210308052421-737401c38b22
+# knative.dev/pkg v0.0.0-20210309024624-0f8d8de5949d
 ## explicit
 knative.dev/pkg/apis
 knative.dev/pkg/apis/duck