chore(deps)(deps): bump k8s.io/apimachinery from 0.33.1 to 0.34.2#45
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
chore(deps)(deps): bump k8s.io/apimachinery from 0.33.1 to 0.34.2#45dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [k8s.io/apimachinery](https://github.com/kubernetes/apimachinery) from 0.33.1 to 0.34.2. - [Commits](kubernetes/apimachinery@v0.33.1...v0.34.2) --- updated-dependencies: - dependency-name: k8s.io/apimachinery dependency-version: 0.34.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
There was a problem hiding this comment.
Pull Request Overview
This PR updates k8s.io/apimachinery from version 0.33.1 to 0.34.2, bringing in associated transitive dependency updates.
Key Changes:
- Bumps primary dependency
k8s.io/apimachineryto version 0.34.2 - Updates
sigs.k8s.io/yamlfrom 1.4.0 to 1.6.0 - Updates several transitive dependencies including cbor, gnostic-models, kube-openapi, and k8s.io/utils
Reviewed Changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| go.mod | Updates direct dependency k8s.io/apimachinery to 0.34.2 and sigs.k8s.io/yaml to 1.6.0; includes transitive dependency updates |
| go.sum | Reflects checksums for all updated dependencies and their transitive dependencies |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+116
to
+117
| go.yaml.in/yaml/v2 v2.4.2 // indirect | ||
| go.yaml.in/yaml/v3 v3.0.4 // indirect |
There was a problem hiding this comment.
Invalid module paths go.yaml.in/yaml/v2 and go.yaml.in/yaml/v3. The correct import paths should be gopkg.in/yaml.v2 and gopkg.in/yaml.v3 respectively. These incorrect paths were likely introduced as transitive dependencies. Please verify the dependency update and ensure the correct module paths are resolved.
Suggested change
| go.yaml.in/yaml/v2 v2.4.2 // indirect | |
| go.yaml.in/yaml/v3 v3.0.4 // indirect |
vivekr-splunk
pushed a commit
that referenced
this pull request
Nov 18, 2025
Add comprehensive dependency management tools and documentation to reduce
Dependabot noise and streamline dependency updates.
Changes:
1. **Updated .github/dependabot.yml**
- Reduced update frequency: weekly → monthly for Go, quarterly for Actions
- Reduced open PR limit: 10 → 5 for Go, 10 → 3 for Actions
- Added dependency grouping to batch related updates:
- kubernetes-core: k8s.io/* packages together
- kubernetes-sigs: sigs.k8s.io/* packages together
- cloud-providers: Azure, AWS SDKs together
- observability: Prometheus, logr together
- testing: Test frameworks together
- Ignore major version updates (require manual review)
- This reduces ~20 individual PRs down to ~5 grouped PRs per month
2. **New: scripts/close-dependabot-issues.sh**
- Automated script to close irrelevant Dependabot issues
- Closes GitHub Actions updates (we pin to commit hashes)
- Closes invalid issues (e.g., Golang 1.24→1.25 when we're on 1.23.0)
- Adds explanatory comments before closing
- Handles 12 current issues: #29-41 (Actions), #34 (invalid)
3. **New: .github/ISSUE_TEMPLATE/dependency-updates-tracking.md**
- Template for creating consolidated dependency update issues
- Includes checklists for testing and validation
- Guides through update process step-by-step
- Reusable for future release cycles
4. **New: docs/post-v0.1.0-dependency-updates.md**
- Complete tracking issue content for v0.2.0 dependency updates
- Categorizes 9 remaining Dependabot issues by priority:
- HIGH: K8s core (#46,#45,#42), controller-runtime (#49), cert-manager (#44)
- MEDIUM: Azure SDK (#48), observability (#39,#43)
- LOW: Testing deps (#47,#38)
- Includes implementation plan, testing checklist, timeline
- Ready to be posted as GitHub issue after v0.1.0 release
Benefits:
- Reduces Dependabot noise from 20+ weekly PRs to 5 monthly grouped PRs
- Provides clear process for handling dependency updates
- Batches related updates for easier testing
- Documents why certain issues are closed
- Creates structured approach for future updates
Impact:
- 12 irrelevant issues can be closed immediately
- 9 valid issues consolidated into one v0.2.0 tracking issue
- Future Dependabot PRs will be grouped and less frequent
Usage:
1. Run: ./scripts/close-dependabot-issues.sh (after v0.1.0 release)
2. Create tracking issue using docs/post-v0.1.0-dependency-updates.md
3. New Dependabot config takes effect immediately
🤖 Generated with Claude Code
Co-Authored-By: Claude <[email protected]>
Author
|
Superseded by #57. |
dependabot
bot
deleted the
dependabot/go_modules/k8s.io/apimachinery-0.34.2
branch
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps k8s.io/apimachinery from 0.33.1 to 0.34.2.
Commits
b72d93dMerge remote-tracking branch 'origin/master' into release-1.34cd8b91cclarify that staging repos are automatically published8c59599add pointer to CONTRIBUTING.md for more details on contributing, clarify read...ec3cea5link to what a staging repository ise4db694docs: clarify that this is a staging repository and not for direct contributions04507a3Merge pull request #132942 from thockin/kyaml50e39b1Merge pull request #132935 from benluddy/cbor-bump-custom-marshalers7d108e8Re-vendor sigs.k8s.io/yaml @ v1.6.058c4eb0Merge pull request #133130 from ylink-lfs/chore/residual_boolptr_removal38a24e6chore: residual boolptr and intptr removalDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)