chore(deps): update minor/patch updates #253
Open
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/minorpatch-updates
branch
from
f452218
to
1b9b1e1
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/minorpatch-updates
branch
from
1b9b1e1
to
d1ef9fb
Compare
ℹ Artifact update noticeFile name: provider/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/minorpatch-updates
branch
8 times, most recently
from
4739363
to
30ec42b
Compare
renovate
bot
force-pushed
the
renovate/minorpatch-updates
branch
from
30ec42b
to
71c57ac
Compare
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.17.5->v0.17.7v3.93.1->v3.95.0v3.137.0->v3.138.01.23.2->1.23.3v0.19.0->v0.20.0v6.0.0->v6.1.0v1.12.0->v1.13.0v1.10.3->v1.12.2Release Notes
anchore/sbom-action (anchore/sbom-action)
v0.17.7Compare Source
Changes in v0.17.7
v0.17.6Compare Source
Changes in v0.17.6
pulumi/pulumi-terraform-bridge (github.com/pulumi/pulumi-terraform-bridge/v3)
v3.95.0Compare Source
What's Changed
Full Changelog: pulumi/pulumi-terraform-bridge@v3.94.0...v3.95.0
v3.94.0Compare Source
What's Changed
Full Changelog: pulumi/pulumi-terraform-bridge@v3.93.1...v3.94.0
pulumi/pulumi (github.com/pulumi/pulumi/sdk/v3)
v3.138.0Compare Source
3.138.0 (2024-11-06)
Features
[backend/diy] Keep computer awake while an update is running
#17699
[backend/service] Keep computer awake while an update is running
#17699
#17675
[cli] Add interactive account selection to pulumi login command
#17618
[cli/display] Colorize selected stack when listing
#17606
[engine] Persist metadata about snapshot integrity errors
#17291
[programgen] Implement package descriptor blocks in PCL to load parameterized packages
#17589
[sdk/nodejs] Support Node.js 23
#17639
Bug Fixes
[docs] Fix spacing and formatting of
stack initcommand's long doc#17534
[engine] Spot skipped-create dependencies even when inputs don't change
#17633
[engine] Normalize URNs in
DeletedWithreferences#17666
[engine] Disable the enviromental GITHUB_TOKEN on 403 responses
#17671
[sdk/go] Overwrite directories in workspace.CopyTemplateFiles when called with force=true
#17695
[sdk/python] Add additional debug information to
ValueErrorandAssertionError#17577
Miscellaneous
[docs] Update function comments to remove outdated DIY backend note
#17563
[yaml] Update YAML to 1.11.2
#17637
golang/go (go)
v1.23.3goreleaser/goreleaser-action (goreleaser/goreleaser-action)
v6.1.0Compare Source
What's Changed
New Contributors
Full Changelog: goreleaser/goreleaser-action@v6.0.0...v6.1.0
jaxxstorm/action-install-gh-release (jaxxstorm/action-install-gh-release)
v1.13.0Compare Source
What's Changed
11bd719by @renovate in https://github.com/jaxxstorm/action-install-gh-release/pull/101New Contributors
Full Changelog: jaxxstorm/action-install-gh-release@v1...v1.13.0
pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
v1.12.2Compare Source
🐛 What's Fixed
The fix for signing legacy zip sdists turned out to be incomplete, so @woodruffw💰 promptly produced another follow-up that updated
pypi-attestationsfrom v0.0.13 to v0.0.15 in #297. This is the only change since the previous release.🪞 Full Diff: pypa/gh-action-pypi-publish@v1.12.1...v1.12.2
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.12.1Compare Source
🐛 What's Fixed
Version v1.12.0 hit several rare corner cases we never considered fully supported, and this release fixes a few of those.
In #294, @webknjaz💰 improved the self-hosted runner experience by pre-installing Python if it's not there, and with #293 the ability to use the action on GitHub Enterprise instances has been restored. The latter should've also fixed the ability to invoke [
pypi-publish][pypi-publish] from nested in-repo composite actions — another exotic use-case that was never tested in our CI.@woodruffw💰 also managed to squeeze in a last-minute fix for detecting legacy
.zipsdists while producing attestations via #295.🪞 Full Diff: pypa/gh-action-pypi-publish@v1.12.0...v1.12.1
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Huge Thanks to all the bug reporters for posting the logs, helping inspect the problems and verify the regression fixes!
v1.12.0Compare Source
⚡️ Why Should You Update?
This is a minor version bump, but it does not add any new user-facing interfaces. Still, I felt like it should not be a patch-release: this update brings significant changes to the action invocation and internal release process.
Previously, each invocation of [
pypi-publish][pypi-publish] required building a container image in the invoking CI job. This was inefficient and added about 30 seconds to the publishing jobs at their startup just to build the container.I wanted to improve this for over three years (#58) and a little over half a year ago @br3ndonland💰 stepped up and offered a very comprehensive solution to the limitation I was hoping to overcome: #230.
Going forward, I'm going to pre-build per-version containers prior to cutting each release. And the action invocations will just pull the image from GitHub Container registry.
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.11.0...v1.12.0
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.11.0Compare Source
🔏 Helping you become a trusted supply chain link 🔗
Two months ago, in v1.10.0, @woodruffw💰 integrated support for generating and uploading PEP 740 digital attestations that can be used as provenance objects when analyzing dependency chains for the integrity.
To make sure it works well, it was implemented as an opt-in, so a relatively small subset of projects was able to try it out, and a few issues have been determined and fixed during this time.
That changes today! This version changes the feature toggle to “on by default”. This means that from now on, every project making use of Trusted Publishing will start producing and publishing digital attestations without having to do any modifications to how they use this action.
@woodruffw💰 flipped the respective toggle in #277 with the possibility to opt-out.
🛠️ Internal Dependencies
@woodruffw💰 bumped
sigstoreto v3.5.1 andpypi-attestationsto v0.0.13 in lock files via #276.🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.3...v1.11.0
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Special Thanks to William for working on improving the supply chain provenance in the ecosystem! The overall effort is tracked @&#https://github.com/pypi/warehouse/issues/15871/15871.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.