-
Notifications
You must be signed in to change notification settings - Fork 1
chore(deps): update go modules #47
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
base: main
Are you sure you want to change the base?
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
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
62c9770
to
671bbac
Compare
|
94998de
to
ebedb46
Compare
a929d7e
to
8cda84e
Compare
test: ACI-4051 add test / refactor activate xcode
6684c99
to
1f26ff2
Compare
ac63267
to
0840ed3
Compare
70604a1
to
a5e9927
Compare
a5e9927
to
7676426
Compare
This PR contains the following updates:
v0.6.0
->v0.6.7
0d21f29
->824e1ba
v1.4.1
->v1.6.0
v2.0.0-alpha.38
->v2.0.0-alpha.40
v1.0.13
->v1.0.15
v0.7.7
->v0.7.8
v0.4.10
->v0.4.12
v4.25.7
->v4.25.9
v1.8.1
->v1.10.1
v1.0.5
->v1.0.10
v1.10.0
->v1.11.1
fc7c04a
->49b9836
fc7c04a
->49b9836
fc7c04a
->49b9836
v1.65.0
->v1.76.0
v1.34.2
->v1.36.10
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
beevik/etree (github.com/beevik/etree)
v1.6.0
Compare Source
Changes
Element
pointers:ChildElementsSeq
,SelectElementsSeq
,FindElementsSeq
, andFindElementsPathSeq
.v1.5.1
Compare Source
Fixes
v1.5.0
Compare Source
Changes
Element
functionCreateChild
, which calls a continuation functionafter creating and adding a child element.
Fixes
ReadSettings
values. WhenAttrSingleQuote
is true,CanonicalAttrVal
is forced to be false.bitrise-io/go-steputils (github.com/bitrise-io/go-steputils/v2)
v2.0.0-alpha.40
Compare Source
v2.0.0-alpha.39
Compare Source
bitrise-io/go-utils (github.com/bitrise-io/go-utils)
v1.0.15
Compare Source
v1.0.14
Compare Source
hashicorp/go-retryablehttp (github.com/hashicorp/go-retryablehttp)
v0.7.8
Compare Source
pkg/xattr (github.com/pkg/xattr)
v0.4.12
Compare Source
What's Changed
Full Changelog: pkg/xattr@v0.4.11...v0.4.12
v0.4.11
Compare Source
What's Changed
Full Changelog: pkg/xattr@v0.4.10...v0.4.11
shirou/gopsutil (github.com/shirou/gopsutil/v4)
v4.25.9
Compare Source
What's Changed
cpu
disk
process
Other Changes
New Contributors
Full Changelog: shirou/gopsutil@v4.25.8...v4.25.9
v4.25.8
Compare Source
Important Change
Starting from this release,
VirtualMemoryStat.Used
on Linux is now calculated based onMemAvailable
inmeminfo
. 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
WillBeDeletedOptOutMemAvailableCalc
totrue
. 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.1
Compare Source
🐛 Fix
v1.0.9 of pflags brought back
ParseErrorsWhitelist
and marked it as deprecatedFull Changelog: spf13/cobra@v1.10.0...v1.10.1
v1.10.0
Compare Source
What's Changed
🚨 Attention!
This version of
pflag
carried a breaking change: it renamedParseErrorsWhitelist
toParseErrorsAllowlist
which can break builds if bothpflag
andcobra
are dependencies in your project.pflag and
cobra, upgrade
pflagto 1.0.8 and
cobrato
1.10.0`pflag
v1.0.9 which keeps the deprecatedParseErrorsWhitelist
More 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.1
Compare Source
🐛 Fixes
Full Changelog: spf13/cobra@v1.9.0...v1.9.1
v1.9.0
Compare Source
✨ Features
🐛 Fixes
🤖 Completions
🧪 Testing
✍🏼 Documentation
🔧 Dependency upgrades
pflag
dependencies 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.10
Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.9...v1.0.10
v1.0.9
Compare Source
What's Changed
Full Changelog: spf13/pflag@v1.0.8...v1.0.9
v1.0.8
Compare Source
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhitelist
struct and correspondingFlagSet.parseErrorsWhitelist
field 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.7
Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.6...v1.0.7
v1.0.6
Compare Source
What's Changed
pkg/flag
compatibility by @mckern in #220New Contributors
Full Changelog: spf13/pflag@v1.0.5...v1.0.6
stretchr/testify (github.com/stretchr/testify)
v1.11.1
Compare Source
This release fixes #1785 introduced in v1.11.0 where expected argument values implementing the stringer interface (
String() string
) with a method which mutates their value, when passed to mock.Mock.On (m.On("Method", <expected>).Return()
) or actual argument values passed to mock.Mock.Called may no longer match one another where they previously did match. The behaviour prior to v1.11.0 where the stringer is always called is restored. Future testify releases may not call the stringer method at all in this case.What's Changed
Full Changelog: stretchr/testify@v1.11.0...v1.11.1
v1.11.0
Compare Source
What's Changed
Functional Changes
v1.11.0 Includes a number of performance improvements.
Fixes
Documentation, Build & CI
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.