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

chore(deps): update azure-ipam (patch) #5846

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 14, 2025

This PR contains the following updates:

Package Update Change
containernetworking/azure-ipam patch v0.2.0 -> v0.2.1
containernetworking/azure-ipam patch v0.0.7 -> v0.0.8

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,every weekend,before 5am every weekday" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@Devinwong
Copy link
Collaborator

Hi @rbtr, I realized you updated azure-ipam earlier here https://github.com/Azure/AgentBaker/pull/4256/files so I assigned this PR to you.
Moving on should I just set you as assignee or all these 4 IDs? "rbtr", "behzad-mir", "QxBytes", "jpayne3506"?
Do you prefer grouping ipam with cni, cns and cilium or you prefer separate ipam?

@renovate renovate bot force-pushed the renovate/patch-azure-ipam branch from 889fefd to 9c5a032 Compare February 14, 2025 22:49
@rbtr
Copy link
Contributor

rbtr commented Feb 14, 2025

@Devinwong all together is fine. is it possible to assign a team(s) instead of individuals?
@Azure/acn-cns-reviewers for CNS;
@Azure/acn-cni-reviewers for CNI, IPAM, and Cilium?
These are the teams which have owner priviliges in Azure/azure-container-networking over these components

@rbtr
Copy link
Contributor

rbtr commented Feb 14, 2025

also wondering why this just showed up? these versions were released some time ago - https://github.com/Azure/azure-container-networking/releases/tag/azure-ipam%2Fv0.2.1

@Devinwong
Copy link
Collaborator

@Devinwong all together is fine. is it possible to assign a team(s) instead of individuals? @Azure/acn-cns-reviewers for CNS; @Azure/acn-cni-reviewers for CNI, IPAM, and Cilium? These are the teams which have owner priviliges in Azure/azure-container-networking over these components

Let me check if Renovate supports group.

@Devinwong
Copy link
Collaborator

also wondering why this just showed up? these versions were released some time ago - https://github.com/Azure/azure-container-networking/releases/tag/azure-ipam%2Fv0.2.1

I think it has been there for a while but I have been updating the configs so it closed and recreated the PR today. In general it should have created the PR within 24 hrs after the release is out.

@renovate renovate bot force-pushed the renovate/patch-azure-ipam branch from 9c5a032 to 1d16b8d Compare February 15, 2025 03:03
@renovate renovate bot force-pushed the renovate/patch-azure-ipam branch from 1d16b8d to 31ceb69 Compare February 15, 2025 06:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants