[RHDEVDOCS-6885] Release notes for Pipelines 1.20.1 #100998
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci
bot
added
the
size/S
|
🤖 Thu Oct 23 13:23:18 - Prow CI generated the docs preview: |
chmouel
reviewed
Oct 23, 2025
anithapriyanatarajan
suggested changes
Oct 23, 2025
ochromy
force-pushed
the
RHDEVDOCS-6885
branch
2 times, most recently
from
9db459c to
4192b53
Compare
openshift-ci
bot
added
size/M
ochromy
force-pushed
the
RHDEVDOCS-6885
branch
from
4192b53 to
acc637d
Compare
modules/op-release-notes-1-20-1.adoc
Outdated
|
|
||
| .User interface | ||
|
|
||
| * Before this update, after upgrading {OCP} to 4.19.15, the Navigation tab intermittently disappeared, and the Pipeline Operator installation UI could crash after creating a PipelineRun on Sandbox clusters. These issues were caused by a race condition introduced by new flags in {OCP}. With this update, the race condition is been resolved and the issue is fixed. |
There was a problem hiding this comment.
@ochromy the issue happens when customers upgrade to any OCP version 4.19.15 or greater until some version this issue is expected the mitigation for which is to upgrade to pipelines versio 1.20.1. Please reconfirm this
There was a problem hiding this comment.
I've updated the note:
- Before this update, after upgrading {OCP} to 4.19.15 or greater, the Navigation tab intermittently disappeared, and the Pipeline Operator installation UI could crash after creating a PipelineRun on Sandbox clusters. These issues were caused by a race condition introduced by new flags in {OCP}. With this update, the race condition is resolved.
@anwesha-palit-redhat Could you please confirm/check this?
srivickynesh
suggested changes
Oct 23, 2025
reviews no1 reviews no2 reviews no3 reviews no4 reviews no5
ochromy
force-pushed
the
RHDEVDOCS-6885
branch
from
acc637d to
6f02127
Compare
|
@ochromy: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
zakisk
reviewed
Oct 24, 2025
|
|
||
| * Before this update, commit status handling and pipeline execution for GitLab forks would fail unexpectedly when {pac} fell back to posting comments for status updates when permissions were restricted on forked projects, and PipelineRuns would fail if the configured token lacked read access to the source repository. With this update, {pac} attempts to set commit status on both the source (fork) and target (upstream) projects, only posting a comment if both attempts fail. Additionally, {pac} attempts to proactively verify that the configured token includes the `read_repository` scope before running a pipeline, failing early with a clear error message if access is insufficient. | ||
|
|
||
| * Before this update, the {pac} dynamic variable `revision` returned the Secure Hash Algorithm (SHA) of the original commit instead of the latest HEAD merge commit after upgrading to {pipelines-shortname} 1.19. With this update, the changes introduced in 1.19 are reverted and the revision variable always fetches the SHA of the HEAD merge commit as expected. |
There was a problem hiding this comment.
Suggested change
| * Before this update, the {pac} dynamic variable `revision` returned the Secure Hash Algorithm (SHA) of the original commit instead of the latest HEAD merge commit after upgrading to {pipelines-shortname} 1.19. With this update, the changes introduced in 1.19 are reverted and the revision variable always fetches the SHA of the HEAD merge commit as expected. | |
| * Before this update, the {pac} dynamic variable `revision` returned the SHA of the original commit instead of the latest HEAD merge commit after upgrading to {pipelines-shortname} 1.19. With this update, the changes introduced in 1.19 are reverted and the `revision` variable always fetches the SHA of the HEAD merge commit as it does before. |
There was a problem hiding this comment.
I guess full form of the SHA doesn't make sense here as we usually onle use term "SHA".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version(s):
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-6885
Link to docs preview:
QE review: