Skip to content

Release v0.42.1#2681

Merged
zakisk merged 2 commits intorelease-v0.42.xfrom
release-v0.42.1
Apr 14, 2026
Merged

Release v0.42.1#2681
zakisk merged 2 commits intorelease-v0.42.xfrom
release-v0.42.1

Conversation

@theakshaypant
Copy link
Copy Markdown
Member

📝 Description of the Change

Commits included:

  • 9b55de3: chore(deps): update grpc and tektoncd/pipeline
  • 4f95d13: fix(gitlab): map skipped status correctly

🔗 Linked GitHub Issue

Fixes #

🧪 Testing Strategy

  • Unit tests
  • Integration tests
  • End-to-end tests
  • Manual testing
  • Not Applicable

🤖 AI Assistance

AI assistance can be used for various tasks, such as code generation,
documentation, or testing.

Please indicate whether you have used AI assistance
for this PR and provide details if applicable.

  • I have not used any AI assistance for this PR.
  • I have used AI assistance for this PR.

Important

Slop will be simply rejected, if you are using AI assistance you need to make sure you
understand the code generated and that it meets the project's standards. you
need at least know how to run the code and deploy it (if needed). See
startpaac to make it easy
to deploy and test your code changes.

If the majority of the code in this PR was generated by an AI, please add a Co-authored-by trailer to your commit message.
For example:

Co-authored-by: Claude noreply@anthropic.com

✅ Submitter Checklist

  • 📝 My commit messages are clear, informative, and follow the project's How to write a git commit message guide. The Gitlint linter ensures in CI it's properly validated
  • ✨ I have ensured my commit message prefix (e.g., fix:, feat:) matches the "Type of Change" I selected above.
  • ♽ I have run make test and make lint locally to check for and fix any
    issues. For an efficient workflow, I have considered installing
    pre-commit and running pre-commit install to
    automate these checks.
  • 📖 I have added or updated documentation for any user-facing changes.
  • 🧪 I have added sufficient unit tests for my code changes.
  • 🎁 I have added end-to-end tests where feasible. See README for more details.
  • 🔎 I have addressed any CI test flakiness or provided a clear reason to bypass it.
  • If adding a provider feature, I have filled in the following and updated the provider documentation:
    • GitHub App
    • GitHub Webhook
    • Gitea/Forgejo
    • GitLab
    • Bitbucket Cloud
    • Bitbucket Data Center

@theakshaypant
Copy link
Copy Markdown
Member Author

Testing skipped gitlab status with this branch
image

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates several dependencies, including google/cel-go, tektoncd/pipeline, and google.golang.org/grpc, and removes the unused go-strcase library. It also updates the CI skip status logic to use a 'skipped' conclusion instead of 'neutral' or 'canceled' within the sinker adapter and GitLab provider. I have no feedback to provide.

@theakshaypant theakshaypant changed the base branch from release-v0.42.0 to release-v0.42.x April 14, 2026 05:13
Upgrade google.golang.org/grpc to v1.79.3 to fix
CVE-2026-33186 (GHSA-p77j-4mvh-x3m3), a critical HTTP/2
:path validation flaw that allows bypassing authorization
rules in gRPC interceptors.

Upgrade github.com/tektoncd/pipeline to v1.9.2 to address
CVE-2026-33211 (GHSA-j5q5-j9gm-2w5c), a path traversal in
the git resolver that could expose ServiceAccount tokens.

Signed-off-by: Akshay Pant <akpant@redhat.com>
Use gitlab.Skipped state instead of gitlab.Canceled when the
conclusion is ConclusionSkipped, so that GitLab pipelines show the
correct skipped status. Also update the skip CI path in the sinker
to use ConclusionSkipped instead of ConclusionNeutral.

Signed-off-by: Akshay Pant <akpant@redhat.com>
@zakisk zakisk merged commit 8300a0f into release-v0.42.x Apr 14, 2026
4 of 13 checks passed
@zakisk zakisk deleted the release-v0.42.1 branch April 14, 2026 07:05
@zakisk zakisk restored the release-v0.42.1 branch April 14, 2026 07:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants