KEMBAR78
Configure Renovate - autoclosed by renovate-bot · Pull Request #5 · googleapis/java-storage · GitHub
Skip to content

Conversation

@renovate-bot
Copy link
Contributor

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

  • google-cloud-storage/pom.xml (maven)

Configuration Summary

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

  • Start dependency updates only once this onboarding 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)
  • 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.


You have configured Renovate to use branch master as base branch.

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

Update dependency com.google.apis:google-api-services-storage to v1-rev20191011-1.30.3
  • Schedule: "at any time"
  • Branch name: renovate/com.google.apis-google-api-services-storage-1.x
  • Merge into: master
  • Upgrade com.google.apis:google-api-services-storage to v1-rev20191011-1.30.3

❓ 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.


Newsflash: Renovate has joined WhiteSource, and is now free for all use. Learn more or view updated terms and privacy policies.

@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:run Add this label to force Kokoro to re-run the tests. label Dec 21, 2019
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Dec 21, 2019
@kokoro-team kokoro-team removed the kokoro:run Add this label to force Kokoro to re-run the tests. label Dec 21, 2019
@renovate-bot renovate-bot changed the title Configure Renovate Configure Renovate - autoclosed Dec 26, 2019
@renovate-bot renovate-bot deleted the renovate/configure branch December 26, 2019 21:28
BenWhitehead added a commit that referenced this pull request May 2, 2022
# This is the 1st commit message:

# This is a combination of 2 commits.
# This is the 1st commit message:

# This is a combination of 2 commits.
# This is the 1st commit message:

wip: first stab at trying to corral all {to,from}Pb methods from model classes

# This is the commit message #2:

wip: refactor all access of ApiaryConversions to use their intermediary `codec` method

# This is the commit message #2:

wip: add clirr rule to allow removing accidental public hmacKeyMetadata#toPb

# This is the commit message #2:

wip: add enum ApiaryConversions#Codecs

# This is the commit message #3:

wip: fix lifecycle rule tests

# This is the commit message #4:

wip: fix blob metadata encoding

# This is the commit message #5:

wip: replace Blob#fromPb and Bucket#fromPb with BlobInfo#asBlob and BucketInfo#asBucket

The old fromPb method were conflating creating an instance of an "Info" model with create an instance of an "Info" model and binding it together with a Storage instance.

Now, an instance of Info model can be decoded (where/whenever) and then turned into a Blob/Bucket as necessary.

# This is the commit message #6:

tersify conversions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants