easimon/maximize-build-space (easimon/maximize-build-space)
### [`v10`](https://togithub.com/easimon/maximize-build-space/releases/tag/v10): Fix: Build Mount folder Ownership
[Compare Source](https://togithub.com/easimon/maximize-build-space/compare/v9...v10)
#### 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
### [`v9`](https://togithub.com/easimon/maximize-build-space/releases/tag/v9): Allow build mount path to be a parent of $GITHUB_WORKSPACE
[Compare Source](https://togithub.com/easimon/maximize-build-space/compare/v8...v9)
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.
### [`v8`](https://togithub.com/easimon/maximize-build-space/releases/tag/v8): Ensure mount point directory exists, allow custom ownership
[Compare Source](https://togithub.com/easimon/maximize-build-space/compare/v7...v8)
- 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](https://togithub.com/dawidd6) for the contribution!
Configuration
📅 Schedule: Branch creation - "on the 2nd and 4th day instance on sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
v7
->v10
Release Notes
easimon/maximize-build-space (easimon/maximize-build-space)
### [`v10`](https://togithub.com/easimon/maximize-build-space/releases/tag/v10): Fix: Build Mount folder Ownership [Compare Source](https://togithub.com/easimon/maximize-build-space/compare/v9...v10) #### 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 ### [`v9`](https://togithub.com/easimon/maximize-build-space/releases/tag/v9): Allow build mount path to be a parent of $GITHUB_WORKSPACE [Compare Source](https://togithub.com/easimon/maximize-build-space/compare/v8...v9) 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. ### [`v8`](https://togithub.com/easimon/maximize-build-space/releases/tag/v8): Ensure mount point directory exists, allow custom ownership [Compare Source](https://togithub.com/easimon/maximize-build-space/compare/v7...v8) - 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](https://togithub.com/dawidd6) for the contribution!Configuration
📅 Schedule: Branch creation - "on the 2nd and 4th day instance on sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.