Gathering detailed insights and metrics for ci-yarn-upgrade
Gathering detailed insights and metrics for ci-yarn-upgrade
Gathering detailed insights and metrics for ci-yarn-upgrade
Gathering detailed insights and metrics for ci-yarn-upgrade
Keep NPM dependencies up-to-date with CI, providing version-to-version diff for each library
npm install ci-yarn-upgrade
Typescript
Module System
Min. Node Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
Apache-2.0 License
85 Stars
232 Commits
12 Forks
2 Watchers
2 Branches
11 Contributors
Updated on Jan 28, 2023
Latest Version
0.7.6
Package Id
ci-yarn-upgrade@0.7.6
Unpacked Size
397.75 kB
Size
308.84 kB
File Count
21
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
This command keeps npm dependencies up-to-date by making pull requests from CI.
This is inspired by bitjourney/ci-npm-update.
yarn global add ci-yarn-upgrade
You can add environment variables using the Project settings > Environment Variables page of your project.
GITHUB_ACCESS_TOKEN
GIT_USER_NAME
and GIT_USER_EMAIL
GIT_USER_NAME
and GIT_USER_EMAIL
for committhis command is pushing from build, so you should add read/write deployment key at Project settings > Checkout SSH keys page of your project.
our complete example is here.
Official Node image contains yarn
command now.
docker:
- image: node:10-alpine
Because ci-yarn-upgrade
uses newer git feature.
run: apk add --update --no-cache git openssh-client
In the example below, the scheculed-upgrade
workflow is configured to run every wednesday at 13:00pm UTC.
jobs:
yarn-upgrade:
docker:
- image: node:10-alpine
steps:
- run: apk add --update --no-cache git openssh-client
- checkout
- run: yarn global add ci-yarn-upgrade
- run: yarn install
- run: ci-yarn-upgrade --execute --verbose;
workflows:
version: 2
scheculed-upgrade:
triggers:
- schedule:
cron: "0 13 * * 3"
filters:
branches:
only:
- master
jobs:
- yarn-upgrade
By default, ci-yarn-upgrade runs in dry-run mode.
ci-yarn-upgrade
this command works locally and output result to standard output.
ci-yarn-upgrade --execute
if you set --execute
, this command push branch to remote, and make a pull request.
Usage: ci-yarn-upgrade [options]
Keep NPM dependencies up-to-date with CI, providing version-to-version diff for each library
Options:
-h, --help output usage information
-V, --version output the version number
-n, --username <username> specify the commit auther name. You may set GIT_USER_NAME to environment variable.
-e, --useremail <useremail> specify the commit auther email. You may set GIT_USER_EMAIL to environment variable.
-t, --token <token> specify personal access token for GitHub. use only for debugging purpose. You should set GITHUB_ACCESS_TOKEN to environment variable.
--execute if you don't specify this option, allows you to test this application.
-L, --latest if you specify this option, upgrades packages ignores the version range specified in package.json
-v, --verbose shows details about the running ci-yarn-upgrade
-k, --keep if you specify this option, keep working branch after all.
--prefix <prefix> specify working branch prefix. default prefix is "yarn-upgrade/"
--workingdir <path> specify project root dir. it contains package.json. default path is /path/to/myproject
--with-shadows if you specify this option, shows shadow dependencies changes.
git clone https://github.com/taichi/ci-yarn-upgrade
cd ci-yarn-upgrade
yarn install
Copyright 2016 taichi
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
project is archived
Details
Reason
Found 0/20 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
61 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More