chore(deps): update rharkor/caching-for-turbo action to v1.8

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
rharkor/caching-for-turbo	action	minor	v1.6 -> v1.8

---

Release Notes

rharkor/caching-for-turbo (rharkor/caching-for-turbo)

v1.8

Compare Source

Release Notes: v1.8 - S3 Provider and Cache Management

New Feature: S3 Storage Provider for Turbo Cache

We're excited to announce the addition of Amazon S3 as a storage provider for your Turborepo cache! This new feature allows teams to store cache artifacts in their own S3 buckets or any S3-compatible storage service.

Key Benefits of S3 Provider:

• Organization-owned infrastructure: Store cache artifacts in your own S3 buckets
• Compatible with S3 alternatives: Works with AWS S3, MinIO, DigitalOcean Spaces, and other S3-compatible storage
• Cross-workflow persistence: Cache persists across workflow runs and different repositories
• Complete control: Manage your cache storage according to your organization's needs

How to Use the S3 Provider:

- name: Cache for Turbo
  uses: rharkor/caching-for-turbo@v1.8
  with:
    provider: s3
    s3-access-key-id: ${{ secrets.S3_ACCESS_KEY_ID }}
    s3-secret-access-key: ${{ secrets.S3_SECRET_ACCESS_KEY }}
    s3-bucket: my-turbo-cache-bucket
    s3-region: us-west-2
    s3-endpoint: https://s3.amazonaws.com # Default S3 endpoint
    s3-prefix: turbogha/ # Optional prefix for cache objects

New Feature: Advanced Cache Management Options

To prevent unbounded growth of your cache storage (especially important with S3), we've introduced powerful cache cleanup options that allow you to set automated policies for cache retention:

Cache Cleanup Options:

• Age-based cleanup: max-age: 1mo - Remove cache entries older than the specified duration
  • Supports various time formats: 1d (1 day), 1w (1 week), 1mo (1 month)
• Count-based cleanup: max-files: 300 - Keep only the specified number of most recent cache entries
  • When exceeded, oldest cache entries are removed first
• Size-based cleanup: max-size: 10gb - Remove oldest entries when total size exceeds the limit
  • Supports various size formats: 100mb, 5gb, 10gb

Example with Cache Management:

- name: Cache for Turbo
  uses: rharkor/caching-for-turbo@v1.8
  with:
    provider: s3
    s3-access-key-id: ${{ secrets.S3_ACCESS_KEY_ID }}
    s3-secret-access-key: ${{ secrets.S3_SECRET_ACCESS_KEY }}
    s3-bucket: my-turbo-cache-bucket
    s3-region: us-west-2

### Cache management configuration
    max-age: 2w    # Remove entries older than 2 weeks
    max-size: 5gb  # Keep total cache size under 5GB
    max-files: 500 # Keep at most 500 cache files

Important Notes:

1. S3 Storage Cost Management: Unlike GitHub's built-in cache, S3 does not automatically prune old entries. We strongly recommend configuring at least one cleanup option to avoid unlimited storage growth and unexpected costs.

2. Required S3 Configuration: When using the S3 provider, you must provide s3-access-key-id, s3-secret-access-key, s3-bucket, s3-region, and s3-endpoint.

3. S3 Compatibility: Works with any S3-compatible storage service by configuring the appropriate endpoint.

Security Best Practices:

Always use GitHub Secrets for storing your S3 credentials:

s3-access-key-id: ${{ secrets.S3_ACCESS_KEY_ID }}
s3-secret-access-key: ${{ secrets.S3_SECRET_ACCESS_KEY }}

This release provides enterprise-grade caching capabilities while keeping you in complete control of your infrastructure and storage costs. Enjoy faster builds with the flexibility of your own storage backend!

Full Changelog: rharkor/caching-for-turbo@v1.7...v1.8

v1.7

Compare Source

What's Changed

• Fix with the new github cache api
• Bump to eslint 9

Full Changelog: rharkor/caching-for-turbo@v1.6...v1.7

---

Configuration

📅 Schedule: Branch creation - "every weekend" (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 was generated by Mend Renovate. View the repository job log.