fix(e2e): bump devenv to 1.65.0#1167
Merged
Merged
Conversation
The e2e pinned devenv version (1.64.7) predates the Velero node-agent memory fix released in devenv v1.65.0. Because the shared orb installs devenv from the pinned version in mise.e2e.toml, every consumer's e2e job (e.g. searchproxy) still runs 1.64.7 and intermittently fails waiting for restic restores to complete. Bump the pin to 1.65.0 and update mise.e2e.lock (checksums + asset IDs verified against the v1.65.0 release).
iamrz1
changed the title
malept
approved these changes
Jul 16, 2026
malept
left a comment
malept
left a comment
Member
There was a problem hiding this comment.
The fix is fine, the PR description is something like a dozen lines too long.
|
Link to code coverage report (posted by coverbot 🤖) |
Contributor
|
🎉 This PR is included in version 2.39.1-rc.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.39.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
2 participants
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.
Please read CONTRIBUTING.md for additional information on contributing to this repository!
What this PR does / why we need it
Bumps the e2e-pinned
devenvversion from 1.64.7 → 1.65.0 (inmise.e2e.toml, withmise.e2e.lockupdated to match).The shared orb's
e2ejob installsdevenvfrom the version pinned inmise.e2e.toml(via mise;devenv_pre_releasedefaults tofalse). That pin was still1.64.7, which predates the Velero node-agent memory fix released in devenvv1.65.0. As a result, every consumer's e2e job (e.g.searchproxy) was still running1.64.7and intermittently failing while waiting for restic (fs-backup) restores to complete:Bumping the pin lets the released fix actually reach e2e once a new orb is cut and adopted.
Jira ID
[XX-XX]
Notes for your reviewers
devenvplatform entries (linux-arm64 (+musl), linux-x64 (+musl), macos-arm64, macos-x64) were cross-checked against the livev1.65.0GitHub release — URLs, sha256 checksums, and numeric asset IDs all match the releasechecksums.txt/asset digests. The-muslvariants intentionally reuse the non-musl tarball, matching the prior1.64.7convention.sharedorb release must be cut and consumers (searchproxy, etc.) must adopt it.~/.local/share/mise) is restored via a time-based prefix key rather than a lockfile hash, so the first runs after merge may still restore a cache containing the old1.64.7binary until the daily cache rotates. mise should re-resolve to1.65.0from the updated lock, but flagging in case a forced cache-bust is desired.