The dependency @adobe/aio-cna-core-config was updated from 1.0.13 to 1.0.14.

🚨 View failing branch.

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

@adobe/aio-cna-core-config 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.

Your Greenkeeper Bot 🌴

Expected Behaviour

https://github.com/adobe/aio-cli/blob/08721fa0f1c257f0f79e8a270dd5f8fd707a2bf3/package.json#L56

Actual Behaviour

Hook up Travis CI to run the unit tests.

The devDependency eslint-plugin-jest was updated from 22.9.0 to 22.10.0.

🚨 View failing branch.

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

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

• Settings ->Branches -> Edit (master) -> Require status checks to pass before merging
• This will only show up if you have a new PR, since it was recently activated

The devDependency eslint-plugin-jest was updated from 22.5.1 to 22.6.0.

🚨 View failing branch.

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

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency codecov was updated from 3.6.2 to 3.6.3.

🚨 View failing branch.

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

codecov is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

This works under node-14, but fails under node-16.
It looks like overriding process.platform breaks under node 16.

 FAIL  test/commands/config/edit.js
  ● get › default - win32

    expect(jest.fn()).toHaveBeenCalledWith(...expected)

    - Expected
    + Received

    - "notepad",
    + "vi",
      ["global"],
      {"detached": true, "stdio": "inherit"},

    Number of calls: 1

      55 |     })
      56 |     return TheCommand.run([]).then(() => {
    > 57 |       expect(childProcess.spawn).toHaveBeenCalledWith('notepad', ['global'], { detached: true, stdio: 'inherit' })
         |                                  ^
      58 |     })
      59 |   })
      60 |

      at test/commands/config/edit.js:57:34

There have been updates to the jest2 monorepo:

• • The devDependency jest-haste-map was updated from 24.8.1 to 24.9.0.

• The devDependency jest-resolve was updated from 24.8.0 to 24.9.0.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the jest2 group definition.

jest2 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

https://github.com/adobe/aio-cna-core-config

Expected Behaviour

Getting the complete configuration with aio config or aio config:get (no key) should return just a JSON document of the current configuration which would also be suitable for input to, say, jq.

Example empty configuration:

$ aio config:get
{}

Example configuration with one property piping out to jq:

$ aio config:set test 5
$ aio config | jq .
{
  "test": "5"
}

Actual Behaviour

The actual output prints a null prototype and then the object in plain JavaScript but non-JSON compliant way:

Example empty configuration:

$ aio config:get
[Object: null prototype] {}

Example configuration with one property:

$ aio config:set test 5
$ aio config
[Object: null prototype] { test: '5' }

Reproduce Scenario (including but not limited to)

See examples above

Steps to Reproduce

See examples above

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

The devDependency @oclif/test was updated from 1.2.2 to 1.2.4.

🚨 View failing branch.

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

@oclif/test is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

File .github/workflows/node.js.yml. See https://github.com/adobe/aio-cli-plugin-app/blob/5670908e7ef7ba63c903ee924520eeb018a9e448/.github/workflows/node.js.yml#L32-L36

Currently all values are stored in plaintext files.
To store sensitive information in a more secure place, I would recommend using something like https://github.com/atom/node-keytar which leverages the system's keychain. That would probably require extending the API so that callers can indicate whether the value is sensitive or not.

Describe the bug
oclif/dev-cli has a bug where it assumes a version tag is prefixed by v when it should respect the setting in .npmrc. See oclif/dev-cli#123

Workaround is setting this key in the plugin's package.json:

"oclif": {
    "repositoryPrefix": "<%- repo %>/blob/<%- version %>/<%- commandPath %>"
  }

To Reproduce
See the section for a command in README.md, the link to the source goes to 404.

Expected behavior
The link works.

Actual behavior
The link does not work.

Expected Behaviour

commands that navigate ( process.chdir ) expect local config files to be loaded from the new cwd

Actual Behaviour

cwd from where the cli is launched is used for eternity and there is no way to reset local config

Sample Code that illustrates the problem

process.chdir('./somedir')
// call some cli plugin command that used config
otherCommand.run(['get','somekey'])

Hook up AppVeyor to run the unit tests on Windows.

• This repo has been migrated to Travis-CI.com, and the Github App has been activated

Description

1. Click on any command link in the README
2. At the bottom of the command, the See code: link points to .ts file

Expected:

It should point to the actual code file, which ends with a .js file extension

• blocked by adobe/aio-lib-core-config#6
• update aio-cna-core-config dep to ^1.0.14

Mock using a fake filesystem.

The devDependency acorn was updated from 6.2.1 to 6.3.0.

🚨 View failing branch.

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

acorn is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Issues covered: https://github.com/adobe/aio-cli-plugin-config/milestone/1

this was implemented over a year ago, to upgrade people from the old config to the new config system.

Expected Behaviour

My previously set config values are still accessible

Actual Behaviour

Only jwt-auth key is migrated to new plugins changed schema

Reproduce Scenario (including but not limited to)

• set some values in config ( latest on npm )
• upgrade to use this implementation
• get the value

Steps to Reproduce

aio config set mySecretKey mySecretValue
git clone adobe/aio-cli-plugin-config
cd aio-cli-plugin-config
npm i
aio plugins link
aio config get mySecretKey

Platform and Version

any/all

Sample Code that illustrates the problem

see repro steps

The devDependency @oclif/test was updated from 1.2.4 to 1.2.5.

🚨 View failing branch.

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

@oclif/test is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

This is just a test. ignore.

test