Skip to content
🤖 A robot that helps you keeping your Scala projects up-to-date
Branch: master
Clone or download
fthomas Merge pull request #354 from fthomas/topic/decouple-auth-from-Http4sG…

Decouple authorization from Http4sGitHubApiAlg
Latest commit b22c430 Mar 20, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
data/images Add round logo Mar 20, 2019
modules Test authentication Mar 20, 2019
project Update scalatest to 3.0.7 Mar 19, 2019
scripts Parse githubApiHost as Uri Mar 9, 2019
.gitignore Ignore .bloop and .metals Dec 12, 2018
.mergify.yml Label PRs from scala-steward automatically Feb 19, 2019
.scalafmt.conf Sort imports Sep 20, 2018
.travis.yml Ensure that docker is available in the build environment Feb 26, 2019 Update Sep 28, 2018
LICENSE Make additional env variables also work with exec if sandbox is disab… Mar 10, 2019
build.sbt Add scalaz-distributed Mar 19, 2019


Build Status codecov Join the chat at Codacy Badge Typelevel project

scala-steward is a robot that helps you keeping library dependencies and sbt plugins up-to-date.

Quick start guide

Open a pull request that adds the GitHub repository of your Scala project to Once that PR is merged, @scala-steward will check periodically for updates of libraries and plugins in your project and will open pull requests in your repository if it can figure out where version numbers need to be updated.

Show us the pull requests!

If you are curious how @scala-steward's pull requests look like, here are the ones it has created so far:


The following people have helped making scala-steward great:


The following companies are using scala-steward to manage their scala dependencies. Using scala-steward in your company and don't see it listed here? Consider creating PR to add your name to the list and join the community.


The scala-steward project supports the Scala Code of Conduct and wants all of its channels (GitHub, Gitter, etc.) to be welcoming environments for everyone.


scala-steward wouldn't exist without the great sbt-updates plugin to determine dependency updates and a bunch of Typelevel and other Scala libraries.

@scala-steward's cute profile picture is by @impurepics.

Running scala-steward

sbt stage

./modules/core/.jvm/target/universal/stage/bin/scala-steward \
  --workspace  "$STEWARD_DIR/workspace" \
  --repos-file "$STEWARD_DIR/" \
  --git-author-name "Scala steward" \
  --git-author-email ${EMAIL} \
  --github-api-host "" \
  --github-login ${LOGIN} \
  --git-ask-pass "$STEWARD_DIR/.github/askpass/$" \
  --env-var FOO=BAR


sbt docker:publishLocal

docker run -v $STEWARD_DIR:/opt/scala-steward -it scala-steward:0.1.0-SNAPSHOT \
  --workspace  "/opt/scala-steward/workspace" \
  --repos-file "/opt/scala-steward/" \
  --git-author-name "Scala steward" \
  --git-author-email ${EMAIL} \
  --github-api-host "" \
  --github-login ${LOGIN} \
  --git-ask-pass "/opt/scala-steward/.github/askpass/$" \
  --env-var FOO=BAR

If you run scala-steward for your own private projects, you can pass additional environment variables from the command line using the --env-var flag as shown in the examples above. You can use this to pass any credentials required by your projects to resolve any private dependencies, e.g.:

--env-var BINTRAY_USER=username
--env-var BINTRAY_PASS=password

These variables will be accessible (in sbt) to all of the projects that scala-steward checks dependencies for.


scala-steward is licensed under the Apache License, Version 2.0.

You can’t perform that action at this time.