Skip to content
This repository has been archived by the owner on Dec 12, 2020. It is now read-only.

[Question] Cannot find preset's package #347

Closed
mrlubos opened this issue Sep 2, 2019 · 5 comments
Closed

[Question] Cannot find preset's package #347

mrlubos opened this issue Sep 2, 2019 · 5 comments
Assignees

Comments

@mrlubos
Copy link

mrlubos commented Sep 2, 2019

Which Renovate are you using? CLI, App, or Pro

App

Which platform are you using? GitHub, GitLab, Bitbucket Azure DevOps

GitHub

Have you checked the logs? Don't forget to include them if relevant

INFO: Renovating repository
DEBUG: Using localDir: /mnt/renovate/gh/helix-re/folio-web
DEBUG: initRepo("helix-re/folio-web")
INFO: Authenticated as user: renovate[bot]
INFO: Using renovate version: 19.36.4
DEBUG: helix-re/folio-web owner = helix-re
DEBUG: helix-re/folio-web default branch = master
DEBUG: Using app token for git init
INFO: Initialising git repository into /mnt/renovate/gh/helix-re/folio-web
INFO: git clone completed
{
  "cloneSeconds": 1.6
}
DEBUG: latest commit
{
  "latestCommitDate": "2019-09-02 15:55:38 +0100"
}
DEBUG: Git private key configured, but not being set
INFO: Setting git author
{
  "gitAuthor": {
    "name": "Renovate Bot",
    "email": "bot@renovateapp.com"
  }
}
DEBUG: resetMemCache()
DEBUG: detectSemanticCommits()
DEBUG: getCommitMessages
DEBUG: Semantic commits detection: unknown
DEBUG: No semantic commits detected
DEBUG: checkOnboarding()
DEBUG: isOnboarded()
DEBUG: findFile(renovate.json)
DEBUG: config file exists
DEBUG: ensureIssueClosing(Action required: Add a Renovate config)
DEBUG: Retrieving issueList
DEBUG: Retrieved 1 issues
DEBUG: Repo is onboarded
DEBUG: Found renovate.json config file
INFO: Repository config
{
  "configFile": "renovate.json",
  "config": {
    "extends": [
      "github>helix-re/renovate-config"
    ],
    "reviewers": []
  }
}
DEBUG: migrateAndValidate()
DEBUG: No config migration necessary
DEBUG: massaged config
{
  "config": {
    "extends": [
      "github>helix-re/renovate-config"
    ],
    "reviewers": []
  }
}
DEBUG: migrated config
{
  "config": {
    "extends": [
      "github>helix-re/renovate-config"
    ],
    "reviewers": []
  }
}
DEBUG: Failed to retrieve default.json from repo
INFO: default.json preset not found - trying renovate.json
DEBUG: Failed to retrieve renovate.json from repo
DEBUG: Preset fetch error
{
  "err": {
    "message": "dep not found",
    "stack": "Error: dep not found\n    at fetchJSONFile (/home/ubuntu/renovateapp/node_modules/renovate/dist/datasource/github/index.js:30:15)\n    at process._tickCallback (internal/process/next_tick.js:68:7)"
  }
}
INFO: Throwing preset error
INFO: Repository has invalid config
{
  "error": {
    "validationError": "Cannot find preset's package (github>helix-re/renovate-config)"
  }
}
DEBUG: raiseConfigWarningIssue()
DEBUG: getBranchPr(renovate/configure)
DEBUG: findPr(renovate/configure, null, open)
DEBUG: Retrieving PR list
DEBUG: Retrieved 968 Pull Requests
DEBUG: ensureIssue()
INFO: Patching issue
INFO: Issue updated
INFO: Finished repository

What is your question?

Our shared configuration lives in a private repository on Github. The package.json includes renovate-config object with the key default and a file called default.json that includes the same contents as package.json>renovate-config>default. How can I fix this please?

@rarkins
Copy link
Collaborator

rarkins commented Sep 2, 2019

You need to make sure Renovate has access to that repo. It’s ok to decline the onboarding pull request to disable renovating it, but it must have access in order to read the files

@mrlubos
Copy link
Author

mrlubos commented Sep 2, 2019

@rarkins Hey, thanks for the prompt response! How can I verify if Renovate has access to the repository?

@rarkins
Copy link
Collaborator

rarkins commented Sep 2, 2019

Have the org admin go to GitHub.com/apps/renovate and check which repos it’s installed into (scroll to bottom IIRC)

@mrlubos
Copy link
Author

mrlubos commented Sep 2, 2019

Thanks a lot @rarkins!

@stale
Copy link

stale bot commented Sep 5, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon if no further activity occurs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants