fix(deps): update all non-major dependencies - #346
Merged
Conversation
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Contributor
Author
ℹ️ Artifact update noticeFile name: ent/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: pgx/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
1 participant
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:
v5.6.0→v5.7.01.42.3→1.43.0v0.43.0→v0.44.0v0.43.0→v0.44.0v0.43.0→v0.44.0v6.2.0→v6.3.09.8.1→9.9.1v1.14.1→v1.14.23.0.11→3.0.126.6.54.Final→6.6.55.FinalWarning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
actions/setup-java (actions/setup-java)
v5.7.0Compare Source
get-convex/convex-backend (convex)
v1.43.0npx convex deployment usageandnpx convex deployment usage-limitsCLI commands toview a deployment’s current resource usage, and
view or edit deployment usage limits.
minuteUTCparameter. When omitted, Convex will automaticallychoose a stable start time within the scheduled hour,
avoiding concentrating jobs at the top of the hour.
commit timestamp
with
ctx.db.vars.commitTs. While the mutation is running,ctx.db.vars.commitTsis a placeholder symbol that isreplaced with a Int64 value at commit time that is guaranteed
to strictly follow commit order, unlike the
_creationTimesystem field.This low-level primitive is helpful for advanced use cases such as implementing
efficient FIFO queues.
v.commitTs()validator that accepts either theupcoming commit timestamp placeholder, or a Int64 commit timestamp.
when using side-by-side TypeScript 6 and 7 installation.
(This setup is used in codebases that want to use the native TypeScript 7
compiler but still need access to the TypeScript compiler JavaScript API.)
typescriptCompilerparameter inconvex.json.This parameter was only necessary when using the TypeScript Native Preview
(@typescript/native-preview). With TypeScript 7, Convex
automatically picks the right binary.
it’s now possible to omit the
envargument fromapp.use(component, { … }).app.use()failed to requirea second argument when a component has required environment variables
(e.g.
app.use(component, { env: { REQUIRED_VAR: "value" } })).usePaginatedQuery_experimentalwhere page splits were handled incorrectly.
testcontainers/testcontainers-go (github.com/testcontainers/testcontainers-go)
v0.44.0Compare Source
What's Changed
🔒 Security
🚀 Features
🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
📦 Dependency updates
gradle/actions (gradle/actions)
v6.3.0Compare Source
Highlights
Enhanced Caching: Windows fixes and a cache-protocol bump
This release updates
gradle-actions-cachingto v1.0.0 (up from v0.7.0), which fixes two significant caching defects, both most visible on Windows:Cache entries failed to store at all on Windows.. Every entry failed
with
Path Validation Error: Path(s) specified in the action for caching do(es) not exist, even though the Gradle User Home was fully intact. Nothing was stored, soevery downstream job ran against an empty Gradle User Home. The cause was a nested,
unpatched copy of
@actions/globcombined with a silently swallowedrequire()inthe bundle, which left Windows path separators unnormalized.
Cache cleanup deleted instrumented jars that were in use. A bug in key
hashing for paths shorter than 64 characters made cleanup judge freshly created
caches/jars-9entries as unused and remove them, so theinstrumented-jarsentrywas never saved and every job re-instrumented its classpaths.
Also included: cache entry names are now consistent between the save and restore
reports — restore previously fell back to showing the raw glob pattern (e.g.
/home/runner/.gradle/caches/modules-*/files-*/*/*/*/*/) instead ofdependencies.Basic caching warns instead of failing silently
The basic (open-source) caching provider now emits a warning and reports
(Entry not saved: save failed)in the Job Summary when a cache save fails, ratherthan reporting success (#1028).
Dependency submission works with Isolated Projects
dependency-submissionnow disables Isolated Projects via a promoted property, sodependency graph generation works on builds that enable it (#1025). Thanks to @reinsch82 for the contribution.
Updated defaults
wrapper-validationWhat's Changed
New Contributors
Full Changelog: gradle/actions@v6.2.0...v6.3.0
Automattic/mongoose (mongoose)
v9.9.1Compare Source
==================
select: falsepaths #12798 BIGSUS24leanwithlean: false#16413v9.9.0Compare Source
==================
pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
v1.14.2Compare Source
This one probably won't touch you visibly so just bookmark @webknjaz's EuroPython 2026 “AI” slop rant for when it's published on YouTube or encourage him to come back with more to share next year!
🛠️ Urgh… Another release!? Again? Explain yourself!
Looking at the diff, you'll only witness updates across the dependency tree. That's it! It's not a security fix or anything like that even, no. But you'll want this update.
🧐 Tell me why..
The rest of the updates bump things related to
pypi-attestationsandsigstore, which has the most interesting backstory here. @facutuesca💰 sent a patch in #417 but a bunch more helped out.TL;DR non-pure-python projects with C-extensions tend to have dozens (sometimes hundreds) wheels to upload to PyPI per release. They are often quite big and take time to transfer over the network. People started noticing problems and coming up with DIY sharding workarounds like aio-libs/aiohttp#13226 around July 23.
On this date, projects with a good amount of bytes to publish would start getting timeouts 5 minutes after the PyPI publishing job begun. The same job that worked just fine before.
I had to start pinging upstream library and ecosystem people, on GitHub and privately, to start making sense of what was happening. Eventually, we collectively concluded that GitHub must've shortened the lifetime of their OIDC identity — it seems to have used to be 10 minutes long (at some point in the past) and is now 5 minutes, apparently. It's not documented clearly, and we have not been able to get any clarity by attempting to contact GitHub through private channels, using personal connections.
Over the course of investigation, @facutuesca💰 found and fixed a related underlying cache invalidation bug in sigstore/sigstore-python#1838, which he then coordinated propagation through the dependency chain updates in sigstore-python, pypi-attestations, gh-action-pypi-publish and gh-action-sigstore-python.
Mike's also discovered that Sigstore's Rekor slowdown seems to have become the main contributing cause of the last week's incident. He's collected some data to support this claim: https://publishing-five-minute-timeout.tiiny.site.
🫶 New Contributors
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.14.1...v1.14.2
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Special Thanks to @davidbrochart💰 and @Dreamsorcerer💰 for turning my attention (in #415 and in private) to the newly surfaced corner case in GitHub's behavior that only affected a narrow category of projects while many others remained blissfully unaware. @bdraco💰 came up with a DIY sharding workaround for aiohttp that served as a demo for other projects. @miketheman💰 confirmed the Warehouse-side details. Also, @jku💰 and @woodruffw💰 helped work through, review and release the Sigstore ecosystem upstream libs.
💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.
bahmutov/start-server-and-test (start-server-and-test)
v3.0.12Compare Source
Bug Fixes
hibernate/hibernate-orm (org.hibernate.orm:hibernate-core)
v6.6.55.FinalConfiguration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Enabled.
♻ 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.