Configure Renovate

[renovate]

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

• pointer_demo/desktop/go.mod (gomod)
• simple_demo/desktop/go.mod (gomod)
• stocks/desktop/go.mod (gomod)
• pointer_demo/android/gradle/wrapper/gradle-wrapper.properties (gradle-wrapper)
• simple_demo/android/gradle/wrapper/gradle-wrapper.properties (gradle-wrapper)
• stocks/android/gradle/wrapper/gradle-wrapper.properties (gradle-wrapper)
• pointer_demo/pubspec.yaml (pub)
• simple_demo/pubspec.yaml (pub)
• stocks/pubspec.yaml (pub)

Configuration Summary

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

• Start dependency updates only once this Configure Renovate PR is merged
• Separate major versions of dependencies into individual branches/PRs
• Do not separate patch and minor upgrades into separate PRs for the same dependency
• Upgrade to unstable versions only if the existing version is unstable
• Raise PRs immediately (after branch is created)
• Use renovate/ as prefix for all branch names
• If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
• Keep existing branches updated even when not scheduled
• Disable automerging feature - wait for humans to merge all PRs
• Ignore node_modules, bower_components, vendor and various test/tests directories
• Update existing lock files only when package.json is modified
• Autodetect whether to pin dependencies or maintain ranges
• Rate limit PR creation to a maximum of two per hour
• Limit to maximum 20 open PRs at any time
• Group known monorepo packages together
• Use curated list of recommended non-monorepo package groupings

🔡 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 7 Pull Requests:

Update dependency gradle to v4.10.3

• Schedule: "at any time"
• Branch name: renovate/gradle-4.x
• Upgrade gradle to 4.10.3

Update dependency http to v0.12.0

• Schedule: "at any time"
• Branch name: renovate/http-0.x
• Upgrade http to 0.12.0

Update dependency intl to v0.15.8

• Schedule: "at any time"
• Branch name: renovate/intl-0.x
• Upgrade intl to 0.15.8

Update dependency intl_translation to v0.17.5

• Schedule: "at any time"
• Branch name: renovate/intl_translation-0.x
• Upgrade intl_translation to 0.17.5

Update module go-flutter-desktop/go-flutter to v0.22.0

• Schedule: "at any time"
• Branch name: renovate/github.com-go-flutter-desktop-go-flutter-0.x
• Upgrade github.com/go-flutter-desktop/go-flutter to v0.22.0

Update module stretchr/objx to v0.2.0

• Schedule: "at any time"
• Branch name: renovate/github.com-stretchr-objx-0.x
• Upgrade github.com/stretchr/objx to v0.2.0

Update dependency gradle to v5

• Schedule: "at any time"
• Branch name: renovate/gradle-5.x
• Upgrade gradle to 5.5.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam 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. View repository job log here.

[GeertJohan]

Should be configured to only PR for go.mod updates.

[pchampio]

Only for go.mod? using renovate for pubspec.yaml is a good idea IMO

[GeertJohan]

Alright!