Cherry-picks and release notes for v0.11.9#7741
Merged
Merged
Conversation
* sdk: Bump engine dependency to v0.11.8 Signed-off-by: Dagger CI <hello@dagger.io> * chore: add release notes for v0.11.8 sdks Signed-off-by: Justin Chadwell <me@jedevc.com> * chore: bump helm dagger version to v0.11.8 Signed-off-by: Justin Chadwell <me@jedevc.com> * docs: bump dagger version to v0.11.8 Signed-off-by: Justin Chadwell <me@jedevc.com> --------- Signed-off-by: Dagger CI <hello@dagger.io> Signed-off-by: Justin Chadwell <me@jedevc.com> Co-authored-by: Dagger CI <hello@dagger.io> Co-authored-by: Justin Chadwell <me@jedevc.com>
Signed-off-by: Justin Chadwell <me@jedevc.com>
* chore: bump internal tooling to use v0.11.8 Signed-off-by: Justin Chadwell <me@jedevc.com> * chore: bump github workers to dagger v0.11.8 Signed-off-by: Justin Chadwell <me@jedevc.com> * chore: update RELEASING Signed-off-by: Justin Chadwell <me@jedevc.com> --------- Signed-off-by: Justin Chadwell <me@jedevc.com>
We used to prune the local cache after sessions ended, but this got dropped during recent refactoring so now the local cache is only being pruned at engine startup. This re-adds that gc call on session disconnect. This is obviously in dire need of integration tests, but setting those up is a decent chunk of work so prioritizing the fix first and will follow-up immediately with that test coverage. For now, I verified the fix manually with a local test that runs an exec that consumes more disk space than my local engines max keep bytes config. Before, the state was never cleared but now I see in the engine logs and in `df` output that it is. Signed-off-by: Erik Sipsma <erik@sipsma.dev>
Signed-off-by: Erik Sipsma <erik@sipsma.dev>
vito
approved these changes
Jun 24, 2024
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
3 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.
Cherry-picks:
Last commit is the standard release notes as generated with instructions already in
RELEASING.md.Note that because this is a separate branch directly off
v0.11.8, this PR is merging into that branch rather than main.release-v0.11.9to avoid conflicts with the tag namev0.11.9that will be made during the actual release.