Skip to content
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

Bump Tekton #1671

Merged

Conversation

SaschaSchwarze0
Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 commented Aug 22, 2024

Changes

I picked the commit from #1664 and made the version of Kubernetes libraries and the Go version consistent. Karan bumped controller-gen.

The 73a8da7 commit is interesting. The integration tests failed on the older Tekton version. Basically the test case retrieved an existing TaskRun from a v0.53 tekton and deserialized it into the v0.62 object. It then applied spec changes and serializes it again to send an update. The update was rejected by Tekton's mutating webhook because it was unable to deserialize this object due to a new property being added in the status. It was only in the status, so I could simply clear it which is not relevant for the update. But, once we observe the same in the future with anything in the spec we may have to revisit our decision to use the latest available LTS version in go.mod rather than the oldest supported LTS version.

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

Release Notes

We now build Shipwright Build with the latest Tekton LTS version

@SaschaSchwarze0 SaschaSchwarze0 added the kind/dependency-change Categorizes issue or PR as related to changing dependencies label Aug 22, 2024
@SaschaSchwarze0 SaschaSchwarze0 added this to the release-v0.14.0 milestone Aug 22, 2024
@openshift-ci openshift-ci bot added the release-note Label for when a PR has specified a release note label Aug 22, 2024
@qu1queee qu1queee self-requested a review August 22, 2024 11:34
@SaschaSchwarze0 SaschaSchwarze0 force-pushed the sascha-bump-tekton branch 2 times, most recently from 131af56 to 90d90bc Compare August 22, 2024 12:29
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 28, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 30, 2024
Copy link
Contributor

@qu1queee qu1queee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 2, 2024
Copy link
Contributor

openshift-ci bot commented Oct 2, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qu1queee

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 2, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit cf21062 into shipwright-io:main Oct 2, 2024
17 checks passed
@SaschaSchwarze0 SaschaSchwarze0 deleted the sascha-bump-tekton branch October 29, 2024 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/dependency-change Categorizes issue or PR as related to changing dependencies lgtm Indicates that a PR is ready to be merged. release-note Label for when a PR has specified a release note
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants