Version updated for easimon/maximize-build-space to version v10. This action is used across all versions by 1,990 repositories. Go to the GitHub Marketplace to find the latest changes. Release notes What’s Changed fix: if the build mount “deleted” / shadowed the GITHUB_WORKSPACE, do not only recreate it, but also ensure it belongs to the correct owner (runner) again Full Changelog: https://github.com/easimon/maximize-build-space/compare/v9...v10

Version updated for easimon/maximize-build-space to version v9. This action is used across all versions by 1,953 repositories. Go to the GitHub Marketplace to find the latest changes. Release notes This release adds support for mounting the build volume over a parent folder of $GITHUB_WORKSPACE. Previously, doing so would remove/shadow the current working directory, and make any later actions/steps fail. New features: Warn about $BUILD_MOUNT_PATH not being empty and list contents in that case Recreate $GITHUB_WORKSPACE afterwards if missing, so following actions have a working directory to start from.

Version updated for easimon/maximize-build-space to version v8. This publisher is shown as ‘verified’ by GitHub. This action is used across all versions by 1,519 repositories. Go to the GitHub Marketplace to find the latest changes. Release notes When using custom mount points, ensure that the specified target directory exists Allow changing ownership of mounted volume (specify as user:group, defaults to runner:runner, which is the default github actions user/group) Thanks to @dawidd6 for the contribution!