kellyselden / boilerplate-update Goto Github PK

View Code? Open in Web Editor NEW

5.0 5.0 7.0 1.6 MB

Update boilerplate code between versions

License: MIT License

JavaScript 100.00%

boilerplate-update's People

Contributors

Stargazers

Watchers

Forkers

burtharris ro0gr phated ziali088 mansona localistico

boilerplate-update's Issues

An in-range update of git-diff-apply is breaking the build 🚨

The dependency git-diff-apply was updated from `0.14.3` to `0.14.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

git-diff-apply is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 4 commits.

0182e47 0.14.4
f33601d move each gitignored file individually
d6fa8d4 failing test for gitignored files in folders
76ee80c clean up regex

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

throw meaningful error when getStartAndEndCommands results in dirs with no files

Instead of

Error: Command failed: git tag v0.0.1
fatal: Failed to resolve 'HEAD' as a valid ref.

sometimes you get tag "vundefined"

An in-range update of git-diff-apply is breaking the build 🚨

The dependency git-diff-apply was updated from `0.14.10` to `0.14.11`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

git-diff-apply is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 2 commits.

f47e23a 0.14.11
d53c2b3 don't delete cwd (because monorepo)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

update deploy key

turn projectType into a list of projectOptions

A single projectType is too limited. This is needed if we want to support vue-cli's wizard style.

Can't use caching logic with Volta

volta-cli/volta#492 (comment)

allow codemods to match other dependencies

For example, match "react-dom" instead of "create-react-app", or match "ember-source" instead of "ember-cli".

Npm install fails with No matching version found for merge-package.json@^3.1.8

➜ ~ npm i -g boilerplate-update
npm ERR! code ETARGET
npm ERR! notarget No matching version found for merge-package.json@^3.1.8

Consider removing direct dependency on npx

The distributed npx library is deprecated and now is handled within the npm distribution.
https://github.com/npm/npx#readme

This means that the npx library being required here will be stuck at v10.2, which in turn requires npm 5.x, which (I think) is sometimes causing problems with ember-cli-update because it uses an older version of graceful-fs.

I realize this is a long cause-and-effect chain of my insinuation. I am experiencing cb.apply is not a function when trying to run ember-cli-update, and so far this is the best guess that I have.

support new codemod property `asyncCommand`

to support ember-cli/ember-cli-update-codemods-manifest#19

Dependency Dashboard

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

Repository problems

These problems occurred while renovating this repository. View logs.

WARN: Using npm packages for Renovate presets is now deprecated. Please migrate to repository-based presets instead.

Warning

These dependencies are deprecated:

Datasource	Name	Replacement PR?
npm	`eslint-plugin-node`
npm	`npx`

Open

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

Replace dependency eslint-plugin-node with eslint-plugin-n ^14.0.0
Update dependency chai to v5
Update dependency chai-as-promised to v8
Update dependency eslint to v9
Update dependency execa to v9
Update dependency sinon to v18
Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/ci.yml

actions/checkout v4

actions/setup-node v4

actions/checkout v4

actions/setup-node v4

actions/checkout v4

actions/setup-node v4

kellyselden/ember-cli-update-action v6

.github/workflows/publish.yml

actions/checkout v4

actions/setup-node v4

npm

package.json

@npmcli/arborist ^7.0.0

cpr ^3.0.1

debug ^4.2.0

execa ^8.0.0

git-diff-apply ^6.0.0

https-proxy-agent ^7.0.0

inquirer ^9.0.0

merge-package.json ^7.0.0

npm-package-arg ^11.0.0

npx ^10.2.0

open ^10.0.0

p-reduce ^3.0.0

pacote ^18.0.0

rimraf ^5.0.0

semver ^7.3.2

tmp 0.2.3

which ^4.0.0

@kellyselden/node-template 5.0.1

chai ^4.3.10

chai-as-promised ^7.1.1

chai-fs ^2.0.0

chai-semver ^1.0.2

chai-string ^1.5.0

eslint ^8.53.0

eslint-config-sane ^1.0.2

eslint-config-sane-node ^1.1.1

eslint-plugin-json-files ^4.1.0

eslint-plugin-mocha ^10.2.0

eslint-plugin-node ^11.1.0

eslint-plugin-prefer-let ^3.0.1

fixturify-project ^7.0.0

fs-extra ^11.0.0

git-fixtures ^8.0.0

mocha ^10.2.0

mocha-helpers ^9.0.0

renovate-config-standard 2.1.2

sinon ^17.0.0

sinon-chai ^3.7.0

standard-node-template 6.0.0

node >=18.12

Check this box to trigger a request for Renovate to run again on this repository