bahmutov / ban-sensitive-files

Checks filenames to be committed against a library of filename rules to prevent sensitive files in Git
62 stars 8 forks source link

Dependency Dashboard #24

Open renovate[bot] opened 4 years ago

renovate[bot] commented 4 years ago

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

[!WARNING] These dependencies are deprecated:

Datasource Name Replacement PR?
npm babel-eslint Available

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Detected dependencies

github-actions
.github/workflows/ci.yml - `actions/checkout v4` - `actions/setup-node v4` - `bahmutov/npm-install v1`
npm
package.json - `bluebird 3.7.2` - `check-more-types 2.24.0` - `debug 4.3.7` - `ggit 2.4.12` - `lazy-ass 1.6.0` - `pluralize 8.0.0` - `ramda 0.30.1` - `update-notifier 5.1.0` - `babel-eslint 10.1.0` - `git-issues 1.3.1` - `husky 9.1.5` - `mocha 10.7.3` - `semantic-release 23.1.1` - `standard 17.0.0`

travi commented 4 years ago

@bahmutov something with the travis config appears to be a bit off. the travis build results are not reporting back for the commits of these renovate PRs.

there was a problem causing npm ci problems, but updating the caching strategy for npm seems to have resolved this. that doesnt appear to have had an impact on the status reporting though.

i've seen similar issues with some of my older personal repos, but havent investigated enough to figure out a resolution before deciding to migrate the project from .org to .com. since i'm not an admin on this repo (not suggesting i should be), i don't have the travis permissions to migrate myself.

do you think migrating to .com is appropriate for this project? if so, would you mind doing so?