Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-8506

Upstream release notes for CLI

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • Pipelines 1.20.0
    • None
    • Tekton CLI
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      1) Before this update, there was a potential panic when trying to read pod logs from already deleted pods, causing application crashes. This is now resolved by properly handling deleted pod scenarios when reading logs.

      2) Before this update, the PipelineRunPending status displayed with incorrect coloring, making it harder to distinguish from other statuses. This is now resolved by updating the Pending color for better visual clarity.

      3) Before this update, there was a deadlock issue when following logs that could cause the application to hang. This is now resolved by fixing the deadlock scenario in the log following functionality.

      4) Before this update, log lines from different tasks and steps were not easily distinguishable, making debugging more difficult. This is now resolved by adding a flag to prefix log lines with log source (task and step name) by default, improving log readability and debugging experience.

      Deprecation ⚠️

      Deprecate the chain command - The chain command is being deprecated as part of ongoing CLI improvements and will be removed in a future release.
      Show
      1) Before this update, there was a potential panic when trying to read pod logs from already deleted pods, causing application crashes. This is now resolved by properly handling deleted pod scenarios when reading logs. 2) Before this update, the PipelineRunPending status displayed with incorrect coloring, making it harder to distinguish from other statuses. This is now resolved by updating the Pending color for better visual clarity. 3) Before this update, there was a deadlock issue when following logs that could cause the application to hang. This is now resolved by fixing the deadlock scenario in the log following functionality. 4) Before this update, log lines from different tasks and steps were not easily distinguishable, making debugging more difficult. This is now resolved by adding a flag to prefix log lines with log source (task and step name) by default, improving log readability and debugging experience. Deprecation ⚠️ Deprecate the chain command - The chain command is being deprecated as part of ongoing CLI improvements and will be removed in a future release.
    • Done

      Story (Required)

      Any relevant RN from upstream needs to be added to the release notes section in a consolidated manner and docs team will be referring to this instead of google docs moving forward.

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      • Drafting the release notes text.
      • Review and approval of release notes.
      • Publication of the release notes.

      Approach (Required)

      • Fetch the list of PRs/issues merged upstream for v1.20 from GitHub (tektoncd/cli repo).
      • Identify PRs relevant to OpenShift Pipelines (skip upstream-only changes not consumed downstream, if applicable).
      • Organize contributions into categories (features, enhancements, bug fixes).

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      RN section is added with a consolidated list of revelant upstream release notes.

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              diagrawa Divyanshu Agrawal
              rh-ee-pbheeman Pavan Mandayam Bheeman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: