coveooss / sfdx-js Goto Github PK
View Code? Open in Web Editor NEWA TypeScript compatible JavaScript wrapper for Salesforce DX CLI.
License: Other
A TypeScript compatible JavaScript wrapper for Salesforce DX CLI.
License: Other
master
branch failed. π¨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. Iβm sure you can resolve this πͺ.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those donβt help, or if this issue is reporting something you think isnβt right, you can always ask the humans behind semantic-release.
An npm token must be created and set in the NPM_TOKEN
environment variable on your CI environment.
Please make sure to create an npm token and to set it in the NPM_TOKEN
environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/
.
Good luck with your project β¨
Your semantic-release bot π¦π
7.5.2
to 7.6.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@commitlint/cli 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.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
master
branch failed. π¨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. Iβm sure you can resolve this πͺ.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those donβt help, or if this issue is reporting something you think isnβt right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project β¨
Your semantic-release bot π¦π
8.1.5
to 8.1.6
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
lint-staged 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.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
7.5.0
to 7.6.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@commitlint/config-conventional 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.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
10.12.8
to 10.12.9
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@types/node 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.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Hi Guys,
The following code;
sfdx.apex.execute({ apexcodefile: 'apex.code', targetusername: 'pkg2' })
Causes the following error
Failed to decipher auth data. reason: Unsupported state or unable to authenticate data
When I run the equivalent command off the command-line, everything is fine.
sfdx force:apex:execute -u pkg2 -f apex.code
Am I missing something about the configuration of your library? or is this a bug?
thanks,
dk-
1.8.13
to 1.8.14
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@types/underscore 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.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
9.2.2
to 9.2.3
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
rollup-plugin-commonjs 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.
The new version differs by 7 commits.
1081282
9.2.3
dbe6a58
Update changelog
a2a0cb1
Add note about monorepo usage (#372)
d93d838
Make generated helper file have .js extension in preserveModules mode (#373)
9755028
Undo version increase to allow for a proper version commit with tag
dc82347
Added support for ancient ES3 browsers (#381)
e2ba623
Fix formatting
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
3.0.3
to 3.0.4
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
coveralls 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.
The new version differs by 5 commits.
8ac4325
version bump
9d9c227
Bump extend from 3.0.1 to 3.0.2 (#226)
33119a7
Bump js-yaml from 3.11.0 to 3.13.1 (#225)
f5549c7
Bump handlebars from 4.1.0 to 4.1.2 (#224)
4df732b
Style fix (#211)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
3.0.7
to 3.1.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
commitizen 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.
The new version differs by 2 commits.
26533fc
feat(cli): Implement --hook option for git hooks integration (#615)
515a57e
docs(readme): document behavior of npx git-cz in non-Commitizen friendly repository (#612)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Updated to 1.0.1. With the code in the README ...
const sfdx = require('sfdx-js').createUsingPath('sfdx')
sfdx.auth.webLogin().then(function () {
console.log('done!');
});
... I now get the error:
const sfdx = require('sfdx-js').createUsingPath('sfdx')
TypeError: require(...).createUsingPath is not a function
The entry point method createUsingPath
should check if its args are A-OK with preconditions.
23.1.4
to 23.10.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
ts-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.
ts-jest
, reloaded!ts-jest
Slack community where you can find some instant helpjest
, typescript
and babel
versionsThe new version differs by 293 commits.
0e5ffed
chore(release): 23.10.0
3665609
Merge pull request #734 from huafu/appveyor-optimizations
45d44d1
Merge branch 'master' into appveyor-optimizations
76e2fe5
ci(appveyor): cache npm versions as well
191c464
ci(appveyor): try to improve appveyor's config
0f31b42
Merge pull request #733 from huafu/fix-test-snap
661853a
Merge branch 'master' into fix-test-snap
aa7458a
Merge pull request #731 from kulshekhar/dependabot/npm_and_yarn/tslint-plugin-prettier-2.0.0
70775f1
ci(lint): run lint scripts in series instead of parallel
a18e919
style(fix): exclude package.json from tslint rules
011b580
test(config): stop using snapshots for pkg versions
7e5a3a1
build(deps-dev): bump tslint-plugin-prettier from 1.3.0 to 2.0.0
fbe90a9
Merge pull request #730 from kulshekhar/dependabot/npm_and_yarn/@types/node-10.10.1
a88456e
build(deps-dev): bump @types/node from 10.9.4 to 10.10.1
54fd239
Merge pull request #729 from kulshekhar/dependabot/npm_and_yarn/prettier-1.14.3
There are 250 commits in total.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
1.16.4
to 1.17.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
prettier 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.
π Release Notes
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Having an issue getting sfdx.org.create( ...
working now. Seemed like it was working in an earlier build, and I was seeing all the supported parameters.
10.11.0
to 10.11.1
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@types/node 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.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency | semantic-release |
Current Version | 15.9.14 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release 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.
The new version differs by 1 commits.
7b8cd99
fix(package): update debug to version 4.0.0
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
7.5.2
to 7.6.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@commitlint/travis-cli 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.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
15.13.11
to 15.13.12
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release 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.
The new version differs by 1 commits.
6f3c21a
fix(package): update resolve-from to version 5.0.0
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
master
branch failed. π¨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. Iβm sure you can resolve this πͺ.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those donβt help, or if this issue is reporting something you think isnβt right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project β¨
Your semantic-release bot π¦π
Add (optional ?) logging.
Log the sfdx-cli command executed at least on a debug/trace level.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.