8000 [cherry-pick] Update debian build stages to use `gpg` over `sq` by pdabelf5 · Pull Request #5665 · nginx/kubernetes-ingress · GitHub
[go: up one dir, main page]
Skip to content

[cherry-pick] Update debian build stages to use gpg over sq #5665

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
May 31, 2024
Merged

[cherry-pick] Update debian build stages to use gpg over sq #5665

merged 1 commit into from
May 31, 2024

Conversation

pdabelf5
Copy link
Collaborator
@pdabelf5 pdabelf5 commented May 30, 2024 •
edited
Loading

Proposed changes

Update debian build stages to use gpg over sq

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING doc
  • I have added tests that prove my fix is effective or that my feature works
  • I have checked that all unit tests pass after adding my changes
  • I have updated necessary documentation
  • I have rebased my branch onto main
  • I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

@pdabelf5 pdabelf5 requested a review from a team as a code owner May 30, 2024 17:48
@jjngx jjngx merged commit 30c71d8 into release-3.5 May 31, 2024
@jjngx jjngx deleted the cherry-pick-gpg-key branch May 31, 2024 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
2 more reviewers

@oseoin oseoin oseoin approved these changes

@jjngx jjngx jjngx approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
None yet
Projects
NGINX Ingress Controller
Archived in project
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@pdabelf5 @oseoin @jjngx @shaun-nx
0