Open
Conversation
ecd336c to
9e81aec
Compare
9e81aec to
b7893f2
Compare
35b2be7 to
75c5447
Compare
8f9a45f to
4675ad1
Compare
3d0f2ca to
ec13e79
Compare
dfb82d7 to
7350b79
Compare
4c84fa1 to
bceec2c
Compare
a2f5704 to
ccac8c3
Compare
ccac8c3 to
28aa2b2
Compare
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
20192f7 to
8a83a44
Compare
6f1b80e to
0727bc5
Compare
2bb6f0a to
564e654
Compare
387c55e to
e0cb764
Compare
840e8b6 to
6ff4a2a
Compare
e2e9d1a to
290696a
Compare
9bab61c to
0162e7c
Compare
91a4c44 to
494f193
Compare
Collaborator
SummaryThis PR updates Go module dependencies with multiple minor and patch version bumps. However, critical issues were found: four dependencies use invalid bare commit hashes instead of proper pseudo-version format, which will cause build failures. Walkthrough
|
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
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.
This PR contains the following updates:
v0.6.0→v0.8.00d21f29→715b73fv1.4.1→v1.6.0v2.0.0-alpha.38→v2.0.0-alpha.48v1.0.13→v1.0.15v2.0.0-alpha.27→v2.0.0-alpha.33v0.7.7→v0.7.8v0.4.10→v0.4.12v4.25.7→v4.26.2v1.8.1→v1.10.2v1.0.5→v1.0.10v1.10.0→v1.11.1fc7c04a→84a4fc4fc7c04a→84a4fc4fc7c04a→84a4fc4v1.65.0→v1.79.2v1.34.2→v1.36.11Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
googleapis/google-cloud-go (cloud.google.com/go/longrunning)
v0.8.0Compare Source
v0.7.0the
blog
post.
Note that although the Spanner service is beta, the Go client library is alpha.
beevik/etree (github.com/beevik/etree)
v1.6.0Compare Source
Changes
Elementpointers:ChildElementsSeq,SelectElementsSeq,FindElementsSeq, andFindElementsPathSeq.v1.5.1Compare Source
Fixes
v1.5.0Compare Source
Changes
ElementfunctionCreateChild, which calls a continuation functionafter creating and adding a child element.
Fixes
ReadSettingsvalues. WhenAttrSingleQuoteis true,CanonicalAttrValis forced to be false.bitrise-io/go-steputils (github.com/bitrise-io/go-steputils/v2)
v2.0.0-alpha.48Compare Source
v2.0.0-alpha.47Compare Source
v2.0.0-alpha.46Compare Source
v2.0.0-alpha.45Compare Source
v2.0.0-alpha.44Compare Source
v2.0.0-alpha.43Compare Source
v2.0.0-alpha.42Compare Source
v2.0.0-alpha.41Compare Source
v2.0.0-alpha.40Compare Source
v2.0.0-alpha.39Compare Source
bitrise-io/go-utils (github.com/bitrise-io/go-utils)
v1.0.15Compare Source
v1.0.14Compare Source
hashicorp/go-retryablehttp (github.com/hashicorp/go-retryablehttp)
v0.7.8Compare Source
pkg/xattr (github.com/pkg/xattr)
v0.4.12Compare Source
What's Changed
Full Changelog: pkg/xattr@v0.4.11...v0.4.12
v0.4.11Compare Source
What's Changed
Full Changelog: pkg/xattr@v0.4.10...v0.4.11
shirou/gopsutil (github.com/shirou/gopsutil/v4)
v4.26.2Compare Source
What's Changed
disk
host
process
Other Changes
New Contributors
Full Changelog: shirou/gopsutil@v4.26.1...v4.26.2
v4.26.1Compare Source
What's Changed
disk
host
mem
process
sensor
New Contributors
Full Changelog: shirou/gopsutil@v4.25.12...v4.26.1
v4.25.12Compare Source
What's Changed
cpu
disk
host
mem
process
New Contributors
Full Changelog: shirou/gopsutil@v4.25.11...v4.25.12
v4.25.11Compare Source
What's Changed
cpu
disk
process
Other Changes
New Contributors
Full Changelog: shirou/gopsutil@v4.25.10...v4.25.11
v4.25.10Compare Source
What's Changed
cpu
disk
host
net
Other Changes
New Contributors
Full Changelog: shirou/gopsutil@v4.25.9...v4.25.10
v4.25.9Compare Source
What's Changed
cpu
disk
process
Other Changes
New Contributors
Full Changelog: shirou/gopsutil@v4.25.8...v4.25.9
v4.25.8Compare Source
Important Change
Starting from this release,
VirtualMemoryStat.Usedon Linux is now calculated based onMemAvailableinmeminfo. This may cause a difference of approximately 6–10% compared to the previous calculation.To address this, we have introduced an opt-out mechanism. You can disable the new calculation by setting the context key
WillBeDeletedOptOutMemAvailableCalctotrue. Please note that this option is undocumented and will be removed in six months (Feb. 2026).For more details, see #1873 and #1882.
What's Changed
cpu
disk
mem
process
Other Changes
New Contributors
Full Changelog: shirou/gopsutil@v4.25.7...v4.25.8
spf13/cobra (github.com/spf13/cobra)
v1.10.2Compare Source
🔧 Dependencies
gopkg.in/yaml.v3togo.yaml.in/yaml/v3by @dims in #2336 - thegopkg.in/yaml.v3package has been deprecated for some time: this should significantly cleanup dependency/supply-chains for consumers ofspf13/cobra📈 CI/CD
🔥✍🏼 Docs
🍂 Refactors
🤗 New Contributors
Full Changelog: spf13/cobra@v1.10.1...v1.10.2
Thank you to our amazing contributors!!!!! 🐍 🚀
v1.10.1Compare Source
🐛 Fix
v1.0.9 of pflags brought back
ParseErrorsWhitelistand marked it as deprecatedFull Changelog: spf13/cobra@v1.10.0...v1.10.1
v1.10.0Compare Source
What's Changed
🚨 Attention!
This version of
pflagcarried a breaking change: it renamedParseErrorsWhitelisttoParseErrorsAllowlistwhich can break builds if bothpflagandcobraare dependencies in your project.pflag andcobra, upgradepflagto 1.0.8 andcobrato1.10.0`pflagv1.0.9 which keeps the deprecatedParseErrorsWhitelistMore details can be found here: #2303 (comment)
✨ Features
🐛 Fix
🪠 Testing
📝 Docs
New Contributors
Full Changelog: spf13/cobra@v1.9.1...v1.9.2
v1.9.1Compare Source
🐛 Fixes
Full Changelog: spf13/cobra@v1.9.0...v1.9.1
v1.9.0Compare Source
✨ Features
🐛 Fixes
🤖 Completions
🧪 Testing
✍🏼 Documentation
🔧 Dependency upgrades
pflagdependencies for v1.9.0 by @jpmcb in #2233Thank you to all of our amazing contributors and all the great work that's been going into the completions feature!!
👋🏼 New Contributors
Full Changelog: spf13/cobra@v1.8.1...v1.9.0
spf13/pflag (github.com/spf13/pflag)
v1.0.10Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.9...v1.0.10
v1.0.9Compare Source
What's Changed
Full Changelog: spf13/pflag@v1.0.8...v1.0.9
v1.0.8Compare Source
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhiteliststruct and correspondingFlagSet.parseErrorsWhitelistfield have been renamed toParseErrorsAllowlist.This should result in compilation errors in any code that uses these fields, which can be fixed by adjusting the names at call sites. There is no change in semantics or behavior of the struct or field referred to by these names. If your code compiles without errors after bumping to/past v1.0.8, you are not affected by this change.
The breaking change was reverted in v1.0.9, by means of re-introducing the old names with deprecation warnings. The plan is still to remove them in a future release, so if your code does depend on the old names, please change them to use the new names at your earliest convenience.
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.7...v1.0.8
v1.0.7Compare Source
What's Changed
New Contributors
Configuration
📅 Schedule: Branch creation - "on Monday at 04:00" (UTC), Automerge - "at 10am on Monday except on 25th of December in 2023 and 1st of January 2024 and 1st of April 2024 and 20th of May 2024 and 19th of August 2024" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.