Fascinated/sharex-php-uploader
2
2
Fork 0
Code Issues 1 Pull Requests 1 Actions Activity

Configure Renovate #9

Merged
Fascinated merged 1 commits from renovate/configure into master 2023-10-15 01:50:13 +00:00
Conversation 0 Commits 1 Files Changed 1 +6
Fascinated commented 2023-10-15 01:48:32 +00:00
Owner
Copy Link

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

  • docker-compose.yml (docker-compose)
  • Dockerfile (dockerfile)
  • .gitea/workflows/upload-image.yaml (github-actions)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

With your current configuration, Renovate will create 5 Pull Requests:

chore(deps): update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: master
  • Upgrade actions/checkout to v4
chore(deps): update dependency ubuntu to v22
  • Schedule: ["at any time"]
  • Branch name: renovate/ubuntu-22.x
  • Merge into: master
  • Upgrade ubuntu to 22.04
chore(deps): update docker/build-push-action action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-5.x
  • Merge into: master
  • Upgrade docker/build-push-action to v5
chore(deps): update docker/login-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-3.x
  • Merge into: master
  • Upgrade docker/login-action to v3
chore(deps): update docker/setup-buildx-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-buildx-action-3.x
  • Merge into: master
  • Upgrade docker/setup-buildx-action to v3

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR has been generated by Renovate Bot.

Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged. --- ### Detected Package Files * `docker-compose.yml` (docker-compose) * `Dockerfile` (dockerfile) * `.gitea/workflows/upload-image.yaml` (github-actions) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding PR is merged - Enable Renovate Dependency Dashboard creation. - Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use. - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories. - Group known monorepo packages together. - Use curated list of recommended non-monorepo package groupings. - Apply crowd-sourced package replacement rules. - Apply crowd-sourced workarounds for known problems with packages. 🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the `renovate.json` in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs. --- ### What to Expect With your current configuration, Renovate will create 5 Pull Requests: <details> <summary>chore(deps): update actions/checkout action to v4</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-checkout-4.x` - Merge into: `master` - Upgrade [actions/checkout](https://github.com/actions/checkout) to `v4` </details> <details> <summary>chore(deps): update dependency ubuntu to v22</summary> - Schedule: ["at any time"] - Branch name: `renovate/ubuntu-22.x` - Merge into: `master` - Upgrade [ubuntu](https://github.com/actions/runner-images) to `22.04` </details> <details> <summary>chore(deps): update docker/build-push-action action to v5</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-build-push-action-5.x` - Merge into: `master` - Upgrade [docker/build-push-action](https://github.com/docker/build-push-action) to `v5` </details> <details> <summary>chore(deps): update docker/login-action action to v3</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-login-action-3.x` - Merge into: `master` - Upgrade [docker/login-action](https://github.com/docker/login-action) to `v3` </details> <details> <summary>chore(deps): update docker/setup-buildx-action action to v3</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-setup-buildx-action-3.x` - Merge into: `master` - Upgrade [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) to `v3` </details> <br /> 🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for `prhourlylimit` for details. --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-config-hash:cbca5a8f0c145b9fd262cdf97b7dc4ce01d337b742cc851095e973b20fb58d06-->
Fascinated added 1 commit 2023-10-15 01:48:32 +00:00
Fascinated merged commit 353c55a1dd into master 2023-10-15 01:50:13 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Fascinated/sharex-php-uploader#9
No description provided.
Delete Branch "renovate/configure"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?