[gferreir]

Changes

Mechanical API version bump for the github-* task family, as part of the
v1beta1 → v1 migration tracked in #1381.

Tasks updated

Task	Old → New	Changes
github-add-comment	0.7 → 0.8	apiVersion v1, minVersion 0.50.0, pinned ubi-minimal:8.2, tests bumped
github-add-gist	0.2 → 0.3	apiVersion v1, minVersion 0.50.0, pinned ubi-minimal:8.2, tests/samples bumped
github-add-labels	0.1 → 0.2	apiVersion v1, minVersion 0.50.0, pinned ubi:8.2, samples bumped
github-app-token	0.2 → 0.3	apiVersion v1, minVersion 0.50.0, samples bumped
github-close-issue	0.2 → 0.3	apiVersion v1, minVersion 0.50.0, pinned ubi:8.2
github-create-deployment	0.2 → 0.3	apiVersion v1, minVersion 0.50.0, pinned ubi-minimal:8.2, tests bumped
github-create-deployment-status	0.1 → 0.2	apiVersion v1, minVersion 0.50.0, pinned ubi-minimal:8.2, tests/samples bumped
github-open-pr	0.2 → 0.3	apiVersion v1, minVersion 0.50.0, pinned python-38:1-34.1599745032, tests bumped
github-request-reviewers	0.1 → 0.2	apiVersion v1, minVersion 0.50.0, tests bumped
github-set-status	0.4 → 0.5	apiVersion v1, minVersion 0.50.0, tests bumped
create-github-release	0.1 → 0.2	apiVersion v1, minVersion 0.50.0, samples bumped

Each task was created using copy-then-modify per CONTRIBUTING.md: one commit
copies the previous version directory, a second commit applies the version bump.
None of these tasks use PipelineResources or other v1beta1-only constructs.

Image pinning

Digests were resolved with skopeo inspect against the current tag:

Image	Digest
registry.access.redhat.com/ubi8/ubi-minimal:8.2	sha256:5cfbaf45ca96806917830c183e9f37df2e913b187aadb32e89fd83fa455ebaa6
registry.access.redhat.com/ubi8/ubi:8.2	sha256:d748c21a55796827da82c61f162b505c59451cba24f1874e5185f21275b6bddc
registry.access.redhat.com/ubi8/python-38:1-34.1599745032	sha256:9a6830a753a77b0a2dc140d05bdf56f35c41867fa06c9b30366216e65bc600b3

Conflict note

#1386 is still open and also creates github-add-comment/0.8 (without an API
bump). This PR starts from current 0.7. If #1386 merges first, this will need
a version rebase to 0.9.

Validation

• yamllint passes for all modified files
• No remaining tekton.dev/v1beta1 references in any of the new version directories

Note on pre-existing conditions

Several of these tasks interpolate $(params.*) directly in script: blocks.
github-set-status still takes its image via a param (default
python:3.10.1-alpine3.15). Those are inherited from the previous versions and
not introduced by this PR. Script injection hardening will be addressed in
follow-up PRs as part of #1381.

Ref: #1381

/kind cleanup

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Follows the authoring recommendations
• Includes docs (if user facing)
• Includes tests (for new tasks or changed functionality)
  • See the end-to-end testing documentation for guidance and CI details.
• Meets the Tekton contributor standards (including functionality, content, code)
• Commit messages follow commit message best practices
• Has a kind label. You can add one by adding a comment on this PR that
  contains /kind <type>. Valid types are bug, cleanup, design, documentation,
  feature, flake, misc, question, tep
• Complies with Catalog Organization TEP, see example. Note An issue has been filed to automate this validation

  • File path follows <kind>/<name>/<version>/name.yaml

  • Has README.md at <kind>/<name>/<version>/README.md

  • Has mandatory metadata.labels - app.kubernetes.io/version the same as the <version> of the resource

  • Has mandatory metadata.annotations tekton.dev/pipelines.minVersion

  • mandatory spec.description follows the convention

      ```
      spec:
        description: >-
          one line summary of the resource
    
          Paragraph(s) to describe the resource.
      ```
    

See the contribution guide for more details.

[tekton-robot]

Diff between version 0.1 and 0.2

diff --git a/task/create-github-release/0.1/README.md b/task/create-github-release/0.2/README.md
index 02747ed..59044b6 100644
--- a/task/create-github-release/0.1/README.md
+++ b/task/create-github-release/0.2/README.md
@@ -13,7 +13,7 @@ Task can also be used to upload multiple `assets` including `binaries` of the re
 ## Install the Task
 
 ```
-kubectl apply -f https://raw.githubusercontent.com/tektoncd/catalog/main/task/create-github-release/0.1/create-github-release.yaml
+kubectl apply -f https://raw.githubusercontent.com/tektoncd/catalog/main/task/create-github-release/0.2/create-github-release.yaml
 ```
 
 ## Parameters
@@ -57,7 +57,7 @@ Release can be created at a particular branch, tag or commit sha, to achieve tha
 required branch, tag or commit sha can be added in the param `commitish`.
 
 Github repository on which release has to be performed must be available in the workspace named `source`. This can be done using 
-[git-clone](https://github.com/tektoncd/catalog/blob/main/task/git-clone/0.1/git-clone.yaml) task as shown [here](../0.1/samples/run.yaml).
+[git-clone](https://github.com/tektoncd/catalog/blob/main/task/git-clone/0.1/git-clone.yaml) task as shown [here](../0.2/samples/run.yaml).
 
 
 To make a release put all the required params, add required secrets and release will be done.
@@ -73,7 +73,7 @@ stringData:
   GITHUB_TOKEN: $(personal_access_token)
 ```
 
-[This](../0.1/samples) example uses ConfigMap for mounting asset file to the workspace, ConfigMap can be created as follows:
+[This](../0.2/samples) example uses ConfigMap for mounting asset file to the workspace, ConfigMap can be created as follows:
 
 ```
 kubectl create configmap upload-asset --from-file=file1.txt --from-file=file2.txt 
diff --git a/task/create-github-release/0.1/create-github-release.yaml b/task/create-github-release/0.2/create-github-release.yaml
index 5347d16..3e3b600 100644
--- a/task/create-github-release/0.1/create-github-release.yaml
+++ b/task/create-github-release/0.2/create-github-release.yaml
@@ -1,11 +1,11 @@
-apiVersion: tekton.dev/v1beta1
+apiVersion: tekton.dev/v1
 kind: Task
 metadata:
   name: create-github-release
   labels:
-    app.kubernetes.io/version: "0.1"
+    app.kubernetes.io/version: "0.2"
   annotations:
-    tekton.dev/pipelines.minVersion: "0.12.1"
+    tekton.dev/pipelines.minVersion: "0.50.0"
     tekton.dev/categories: Git
     tekton.dev/tags: github
     tekton.dev/displayName: "create github release"
diff --git a/task/create-github-release/0.1/samples/run.yaml b/task/create-github-release/0.2/samples/run.yaml
index ae27760..1a08c20 100644
--- a/task/create-github-release/0.1/samples/run.yaml
+++ b/task/create-github-release/0.2/samples/run.yaml
@@ -1,4 +1,4 @@
-apiVersion: tekton.dev/v1beta1
+apiVersion: tekton.dev/v1
 kind: Pipeline
 metadata:
   name: create-github-release-pipeline
@@ -45,7 +45,7 @@ spec:
         - name: release-notes
           workspace: release-notes
 ---
-apiVersion: tekton.dev/v1beta1
+apiVersion: tekton.dev/v1
 kind: PipelineRun
 metadata:
   name: create-github-release-pipeline-run

[gferreir]

/assign @vdemeester

[vdemeester]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment