Skip to content

Update dependency sbt/sbt to v0.13.18#3

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/sbt-sbt-0.x
Open

Update dependency sbt/sbt to v0.13.18#3
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/sbt-sbt-0.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 16, 2024

Mend Renovate

This PR contains the following updates:

Package Update Change
sbt/sbt patch 0.13.0 -> 0.13.18

Release Notes

sbt/sbt (sbt/sbt)

v0.13.18: 0.13.18

Compare Source

v0.13.17: 0.13.17

Compare Source

Improvements
Bug fixes
Internal

v0.13.16: 0.13.16

Compare Source

Fixes with compatibility implications
  • Removes the "hit [ENTER] to switch to interactive mode" feature. Run sbt xxx shell to stay in shell after xxx. #​3091/#​3153 by @​dwijnand
Improvements
  • Improves the new startup messages. See below.
  • Ports sbt-cross-building's ^ and ^^ commands for plugin cross building. See below.
  • Adds Zero scope component for sbt 1.0 compatibility. #​3179 by @​eed3si9n
  • Backports withXXX methods for ModuleID and Artifact for sbt 1.0 compatibility. #​3215 by @​eed3si9n
Bug fixes
  • Fixes the new startup messages. See below.
  • Fixes forward compatibility of Scripted plugin with sbt 1.0.0-RC2. #​3329 by @​dwijnand
  • Fixes ScalaTest nested suite test names being reported as "(It is not a test)". #​3154 by @​jameskoch
  • Fixes default scalaBinaryVersion for Dotty. #​3152 by @​smarter
  • Updates JLine dependency to 2.14.4 to work around ncurses change causing NumberFormatException. #​3265 by @​Rogach
sbt-cross-building

@​jrudolph's sbt-cross-building is a plugin author's plugin.
It adds cross command ^ and sbtVersion switch command ^^, similar to + and ++,
but for switching between multiple sbt versions across major versions.
sbt 0.13.16 merges these commands into sbt because the feature it provides is useful as we migrate plugins to sbt 1.0.

To switch the sbtVersion in pluginCrossBuild from the shell use:

^^ 1.0.0-RC2

Your plugin will now build with sbt 1.0.0-RC2 (and its Scala version 2.12.2).

If you need to make changes specific to a sbt version, you can now include them into src/main/scala-sbt-0.13,
and src/main/scala-sbt-1.0, where the binary sbt version number is used as postfix.

To run a command across multiple sbt versions, set:

crossSbtVersions := Vector("0.13.15", "1.0.0-RC2")

Then, run:

^ compile

#​3133 by @​eed3si9n

Eviction warning presentation

sbt 0.13.16 improves the eviction warning presentation.

Before:

[warn] There may be incompatibilities among your library dependencies.
[warn] Here are some of the libraries that were evicted:
[warn]  * com.google.code.findbugs:jsr305:2.0.1 -> 3.0.0
[warn] Run 'evicted' to see detailed eviction warnings

After:

[warn] Found version conflict(s) in library dependencies; some are suspected to be binary incompatible:
[warn]
[warn]      * com.typesafe.akka:akka-actor_2.12:2.5.0 is selected over 2.4.17
[warn]          +- de.heikoseeberger:akka-log4j_2.12:1.4.0            (depends on 2.5.0)
[warn]          +- com.typesafe.akka:akka-parsing_2.12:10.0.6         (depends on 2.4.17)
[warn]          +- com.typesafe.akka:akka-stream_2.12:2.4.17 ()       (depends on 2.4.17)
[warn]
[warn] Run 'evicted' to see detailed eviction warnings

#​3202 by @​eed3si9n

Improvements and bug fixes to the startup messages

sbt writes out the sbt.version in project/build.properties if it is missing.
sbt 0.13.16 fixes the logging when it happens by using the logger.

We encourage the use of the sbt shell by running sbt, instead of running sbt compile from the terminal repeatedly.
The sbt shell keeps the JVM warm, and there is a significant performance improvement gained for your compilation.
The startup message that we added in sbt 0.13.15 was a bit too aggressive, so we are toning it down in 0.13.16.
It will only be triggered for sbt compile, and it can also be suppressed with suppressSbtShellNotification := true.

#​3091/#​3097/#​3147 by @​dwijnand

v0.13.15: 0.13.15

Compare Source

Fixes with compatibility implications
  • sbt 0.13.15 removes the Maven version range when possible. See below.
Improvements
  • Adds preliminary compatibility with JDK 9. Using this requires 0.13.15+ launcher. #​2951/143 by @​retronym
  • Adds "local-preloaded" repository for offline installation. See below.
  • Notifies and enables users to stay in sbt's shell on the warm JVM by hitting [ENTER] while sbt is running. #​2987/#​2996 by @​dwijnand
  • Adds an Append instance to support sourceGenerators += Def.task { ... }, instead of needing .taskValue. #​2943 by @​eed3si9n
  • Writes out the sbt.version in project/build.properties if it is missing. #​754/#​3025 by @​dwijnand
  • XML generated by JUnitXmlTestsListener now correctly flags ignored, skipped and pending tests. #​2198/#​2854 by @​ashleymercer
  • When sbt detects that the project is compiled with dotty, it now automatically
    sets scalaCompilerBridgeSource correctly, this reduces the boilerplate needed
    to make a dotty project. Note that dotty support in sbt is still considered
    experimental and not officially supported, see dotty.epfl.ch for
    more information. #​2902 by @​smarter
  • Updates sbt new's reference implementation to Giter8 0.7.2.
  • ScriptedPlugin: Add the ability to paginate scripted tests.
    It is now possible to run a subset of scripted tests in a directory at once,
    for example:
    scripted source-dependencies/*1of3
    Will create three pages and run page 1. This is especially useful when running
    scripted tests on a CI, to benefit from the available parallelism. 3013 by @​smarter
Bug fixes
Maven version range improvement

Previously, when the dependency resolver (Ivy) encountered a Maven version range such as [1.3.0,)
it would go out to the Internet to find the latest version.
This would result to a surprising behavior where the eventual version keeps changing over time
even when there's a version of the library that satisfies the range condition.

Starting sbt 0.13.15, some Maven version ranges would be replaced with its lower bound
so that when a satisfactory version is found in the dependency graph it will be used.
You can disable this behavior using the JVM flag -Dsbt.modversionrange=false.

#​2954 by @​eed3si9n

Offline installation

sbt 0.13.15 adds two new repositories called "local-preloaded-ivy"
and "local-preloaded" that point to ~/.sbt/preloaded/.
The purpose for the repositories is to preload them with
sbt artifacts so the installation of sbt will not require access to the Internet.

This also improves the startup time of sbt when you first run it
since the resolution happens off of a local-preloaded repository.

#​2993/#​145 by @​eed3si9n

Notes

No changes should be necessary to your project definition and all plugins published for sbt 0.13.{x|x<14} should still work.

See Migrating from sbt 0.12.x for details on the old operator deprecation.

Special thanks to the contributors for making this release a success. According to git shortlog -sn --no-merges v0.13.13..0.13.15, compared to 0.13.13, there were 64 (non-merge) commits, by eleven contributors: Eugene Yokota, Dale Wijnand, Guillaume Martres, Jason Zaugg, Lars Hupel, Petro Verkhogliad, Eric Richardson, Claudio Bley, Haochi Chen, Paul Draper, Ashley Mercer. Thank you!

v0.13.14

Compare Source

0.13.14 is dead on arrival. https://github.com/sbt/sbt/issues/3086

v0.13.13: 0.13.13

Compare Source

Fixes with compatibility implications
  • Deprecates the old sbt 0.12 DSL, to be removed in sbt 1.0. See below for more details.
  • The .value method is deprecated for input tasks. Calling .value on an input key returns an InputTask[A],
    which is completely unintuitive and often results in a bug. In most cases .evaluated should be called,
    which returns A by evaluating the task.
    Just in case InputTask[A] is needed, .inputTaskValue method is now provided. #​2709 by @​eed3si9n
  • sbt 0.13.13 renames the early command --<command> that was added in 0.13.1 to early(<command>). This fixes the regression #​1041. For backward compatibility --error, --warn, --info, and --debug will continue to function during the 0.13 series, but it is strongly encouraged to migrate to the single hyphen options: -error, -warn, -info, and -debug. #​2742 by @​eed3si9n
  • Improve show when key returns a Seq by showing the elements one per line. Disable with -Dsbt.disable.show.seq=true. #​2755 by @​eed3si9n
  • Recycles classloaders to be anti-hostile to JIT. Disable with -Dsbt.disable.interface.classloader.cache=true. #​2754 by @​retronym
Improvements
  • Adds new command and templateResolverInfos. See below for more details.
  • Auto plugins can add synthetic subprojects. See below for more details.
  • Supports wildcard exclusions in POMs #​1431/sbt/ivy#22/#​2731 by @​jtgrabowski
  • Adds the ability to call aggregateProjects(..) for the current project inside a build sbt file. #​2682 by @​xuwei-k
  • Adds .jvmopts support to the launcher script. sbt/sbt-launcher-package#111 by @​fommil
  • Adds .java-version support to the Windows launcher script. sbt/sbt-launcher-package#111 by @​fommil
  • The startup log level is dropped to -error in script mode using scalas. #​840/#​2746 by @​eed3si9n
  • Adds CrossVersion.patch which sits in between CrossVersion.binary and CrossVersion.full in that it strips off any
    trailing -bin-... suffix which is used to distinguish variant but binary compatible Scala toolchain builds. Most things
    which are currently CrossVersion.full (eg. Scala compiler plugins, esp. macro-paradise) would be more appropriately
    depended on as CrossVersion.patch from this release on.
Bug fixes
new command and templateResolverInfos

sbt 0.13.13 adds a new command, which helps create new build definitions.
The new command is extensible via a mechanism called the template resolver.
A template resolver pattern matches on the passed in arguments after new,
and if it's a match it will apply the template.

As a reference implementation, template resolver for Giter8 is provided. For instance:

sbt new eed3si9n/hello.g8

will run eed3si9n/hello.g8 using Giter8.

#​2705 by @​eed3si9n

Synthetic subprojects

sbt 0.13.13 adds support for AutoPlugins to define subprojects programmatically,
by overriding the extraProjects method:

import sbt._, Keys._

object ExtraProjectsPlugin extends AutoPlugin {
  override def extraProjects: Seq[Project] =
    List("foo", "bar", "baz") map generateProject

  def generateProject(id: String): Project =
    Project(id, file(id)).
      settings(
        name := id
      )
}

In addition, subprojects may be derived from an existing subproject
by overriding derivedProjects:

import sbt._, Keys._

object DerivedProjectsPlugin extends AutoPlugin {
  // Enable this plugin by default
  override def requires: Plugins = sbt.plugins.CorePlugin
  override def trigger = allRequirements

  override def derivedProjects(proj: ProjectDefinition[_]): Seq[Project] =
    // Make sure to exclude project extras to avoid recursive generation
    if (proj.projectOrigin != ProjectOrigin.DerivedProject) {
      val id = proj.id + "1"
      Seq(
        Project(id, file(id)).
          enablePlugins(DatabasePlugin)
      )
    }
    else Nil
}

#​2532/#​2717/#​2738 by @​eed3si9n

Deprecate old sbt 0.12 DSL

The no-longer-documented operators <<=, <+=, and <++= and tuple enrichments are deprecated,
and will be removed in sbt 1.0.

Generally,

task3 <<= (task1, task2) map { (t1, t2) => println(t1 + t2); t1 + t2 }

should migrate to

task3 := {
  println(task1.value + task2.value)
  task1.value + task2.value
}

Except for source generators, which requires task values:

sourceGenerators in Compile <+= buildInfo

This becomes:

sourceGenerators in Compile += buildInfo.taskValue

Another exception is input task:

run <<= docsRunSetting

This becomes:

run := docsRunSetting.evaluated

See Migrating from sbt 0.12.x for more details.

#​2716/#​2763/#​2764 by @​eed3si9n and @​dwijnand

Notes

No changes should be necessary to your project definition and all plugins published for sbt 0.13.{x|x<12} should still work.

Special thanks to the contributors for making this release a success. According to git shortlog -sn --no-merges v0.13.12..v0.13.13, compared to 0.13.12, there were 63 (non-merge) commits, by 9 contributors: Eugene Yokota, Dale Wijnand, Martin Duhem, Miles Sabin, Jaroslaw Grabowski, Kenji Yoshida, Jason Zaugg, Paul Draper, Björn Antonsson. Thank you!

v0.13.12: 0.13.12

Compare Source

Fixes with compatibility implications
  • By default the Scala toolchain artifacts are now transitively resolved using the provided scalaVersion and
    scalaOrganization. Previously a user specified scalaOrganization would not have affected transitive
    dependencies on, eg. scala-reflect. An Ivy-level mechanism is used for this purpose, and as a consequence
    the overriding happens early in the resolution process which might improve resolution times, and as a side
    benefit fixes #​2286. The old behavior can be restored by adding
    ivyScala := { ivyScala.value map {_.copy(overrideScalaVersion = sbtPlugin.value)} }
    to your build. #​2286/#​2634 by @​milessabin
  • The Build trait is deprecated in favor of the .sbt format #​2530 by @​dwijnand
Improvements
  • When RecompileOnMacroDef is enabled, sbt will now print out a info level log indicating that some sources are being recompiled because it's used from a source that contains a macro definition. Can be disabled with incOptions := incOptions.value.withLogRecompileOnMacro(false) #​2637/#​2659 by @​eed3si9n/@​dwijnand
  • Adds Windows script support and native file extensions on Unix platforms. #​2603 by @​ekrich
  • Improves loading time of large builds. #​2630 by @​eed3si9n
  • Adds the ability to call dependsOn for the current project inside a .sbt file. #​2653 by @​anatolydwnld
Bug fixes
Notes

No changes should be necessary to your project definition and all plugins published for sbt 0.13.{x|x<12} should still work. Please report any issues you encounter if this is not the case.

Special thanks to the contributors for making this release a success. According to git shortlog -sn --no-merges v0.13.11..0.13.12, compared to 0.13.11, there were 83 (non-merge) commits, by 11 contributors: Eugene Yokota, Martin Duhem, Grzegorz Kossakowski, Dale Wijnand, Guillaume Martres, Jason Zaugg, Miles Sabin, Tim Harper, ddworak, ekrich, Anatoly Fayngelerin. Thank you!

v0.13.11: 0.13.11

Compare Source

Fixes with compatibility implications
  • JCenter is now opt-in. A new setting useJCenter can be set to true to re-include it, as the first external resolver to find library dependencies. #​2217/#​2467 by @​eed3si9n
  • Adds withInterProjectFirst to the update option, which is enabled by default. When set to true, inter-project resolver will be prioritized above all resolvers and Ivy cache. #​1827 by @​eed3si9n
  • Fixes update option's withLatestSnapshots so it handles modules without an artifact. This flag will be enabled by default.
    #​1514/#​1616/#​2313 by @​eed3si9n
  • No longer passes -J<flag> options to the local Java compiler. #​1968/#​2272 by @​Duhemm
  • Fixes auto imports for auto plugins in global configuration files. Because this is not source compatible with 0.13.x, the fix is enabled only when sbt.global.autoimport flag is true. #​2120/#​2399 by @​timcharper
Improvements
Bug fixes
Configurable Scala compiler bridge

sbt 0.13.11 adds scalaCompilerBridgeSource setting to specify the compiler brigde source. This allows different implementation of the bridge for Scala versions, and also allows future versions of Scala compiler implementation to diverge. The source module will be retrieved using library management configured by bootIvyConfiguration task.

#​2106/#​2197/#​2336 by @​Duhemm

Dotty awareness

sbt 0.13.11 will assume that Dotty is used when scalaVersion starts with 0..
The built-in compiler bridge in sbt does not support Dotty,
but a separate compiler bridge is being developed at smarter/dotty-bridge and
an example project that uses it is available at smarter/dotty-example-project.

#​2344 by @​smarter

Inter-project dependency tracking

sbt 0.13.11 adds trackInternalDependencies and exportToInternal settings. These can be used to control whether to trigger compilation of a dependent subprojects when you call compile. Both keys will take one of three values: TrackLevel.NoTracking, TrackLevel.TrackIfMissing, and TrackLevel.TrackAlways. By default they are both set to TrackLevel.TrackAlways.

When trackInternalDependencies is set to TrackLevel.TrackIfMissing, sbt will no longer try to compile internal (inter-project) dependencies automatically, unless there are no *.class files (or JAR file when exportJars is true) in the output directory. When the setting is set to TrackLevel.NoTracking, the compilation of internal dependencies will be skipped. Note that the classpath will still be appended, and dependency graph will still show them as dependencies. The motivation is to save the I/O overhead of checking for the changes on a build with many subprojects during development. Here's how to set all subprojects to TrackIfMissing.

lazy val root = (project in file(".")).
  aggregate(....).
  settings(
    inThisBuild(Seq(
      trackInternalDependencies := TrackLevel.TrackIfMissing,
      exportJars := true
    ))
  )

The exportToInternal setting allows the dependee subprojects to opt out of the internal tracking, which might be useful if you want to track most subprojects except for a few. The intersection of the trackInternalDependencies and exportToInternal settings will be used to determine the actual track level. Here's an example to opt-out one project:

lazy val dontTrackMe = (project in file("dontTrackMe")).
  settings(
    exportToInternal := TrackLevel.NoTracking
  )

#​2266/#​2354 by @​eed3si9n

Def.settings

Using Def.settings it is now possible to nicely define settings as such:

val modelSettings = Def.settings(
  sharedSettings,
  libraryDependencies += foo
)

#​2151 by @​dwijnand

Notes

No changes should be necessary to your project definition and all plugins published for sbt 0.13.{x|x<11} should still work. Please report any issues you encounter if this is not the case.

Special thanks to the contributors for making this release a success. According to git shortlog -sn --no-merges v0.13.9..v0.13.11, [compared to 0.13.9][3], there were 201 (non-merge) commits, by 19 contributors: Martin Duhem, Eugene Yokota, Dale Wijnand, Stu Hood, Adriaan Moors, Pierre DAL-PRA, Grzegorz Kossakowski, fkorotkov, Josh Suereth, Huw Giddens, Tim Harper, Guillaume Martres, Antonio Cunei, Krzysztof Romanowski, David Perez, Jason Zaugg, Jacek Laskowski, Johannes Rudolph, Jonas Fonseca. Thank you!

v0.13.9: 0.13.9

Compare Source

Fixes with compatibility implications
  • Starting 0.13.9, crossScalaVersions default value is fixed back to the older 0.12.x behavior. See below for details.
  • Starting 0.13.9, the generated POM files no longer include dependencies on source or javadoc jars obtained via withSources() or withJavadoc(). See below for details.
  • Scala version is bumped to 2.10.5. This brings in the fix for SI-9027: XML node sequence literal bug. #​1666/#​2068 by @​eed3si9n
Improvements
Bug fixes
  • Fixes memory/performance/correctness issue with cached resolution. See below.
  • Correct incremental compile debug message for invalidated products #​1961 by @​jroper
  • Enables forced GC by default. See below.
  • Fixes Maven compatibility to read maven-metadata.xml. See below.
  • Captures errors on help command. #​1900/#​1940 by @​DavidPerezIngeniero
  • Prevents history command(s) from going into an infinite loop #​1562 by @​PanAeon
  • Honors overwrite flag when publishing locally. #​1960 by @​asflierl
  • Fixes a certain class of pom corruption that can occur in the presence of parent-poms. #​1856 by @​jsuereth
  • Adds dependency-level exclusions in the POM for project-level exclusions. #​1877/#​2035 by @​dwijnand
crossScalaVersions default value

As of this fix crossScalaVersions returns to the behaviour present in 0.12.4 whereby it defaults to what
scalaVersion is set to, for example if scalaVersion is set to "2.11.6", crossScalaVersions now defaults
to Seq("2.11.6").

Therefore when upgrading from any version between 0.13.0 and 0.13.8 be aware of this new default if
your build setup depended on it.

#​1828/#​1992 by @​dwijnand

POM files no longer include certain source and javadoc jars

When declaring library dependencies using the withSources() or withJavadoc() options, sbt was also including
in the pom file, as dependencies, the source or javadoc jars using the default Maven scope. Such dependencies
might be erroneously processed as they were regular jars by automated tools

#​2001/#​2027 by @​cunei

retrieveManaged related improvements

sbt 0.13.9 adds retrieveManagedSync key that, when set to true, enables synchronizing retrieved to the current build by removed unneeded files.

It also adds configurationsToRetrieve key, that takes values of Option[Set[Configuration]]. If set, when retrieveManaged is true only artifacts in the specified configurations will be retrieved to the current build.

#​1950/#​1987 by @​ajsquared

Cached resolution fixes

On a larger dependency graph, the JSON file growing to be 100MB+
with 97% of taken up by caller information.
To make the matter worse, these large JSON files were never cleaned up.

sbt 0.13.9 filters out artificial or duplicate callers,
which fixes OutOfMemoryException seen on some builds.
This generally shrinks the size of JSON, so it should make the IO operations faster.
Dynamic graphs will be rotated with directories named after yyyy-mm-dd,
and stale JSON files will be cleaned up after few days.

sbt 0.13.9 also fixes a correctness issue that was found in the earlier releases.
Under some circumstances, libraries that shouldn't have been evicted was being evicted.
This occured when library A1 depended on B2, but a newer A2 dropped the dependency,
and A2 and B1 are also is in the graph. This is fixed by sorting the graph prior to eviction.

#​2030/#​1721/#​2014/#​2046/#​2097/#​2129 by @​eed3si9n

Force GC

@​cunei in #​1223 discovered that sbt leaks PermGen
when it creates classloaders to call Scala Compilers.
sbt 0.13.9 will call GC on a set interval (default: 60s).
It will also call GC right before cross building.
This behavior can diabled using by setting false to forcegc
setting or sbt.task.forcegc flag.

#​1773 by @​eed3si9n

Maven compatibility fix

To resolve dynamic versions such as SNAPSHOT and version ranges, the dependency resolution engine
queries for the list of available versions.
For Maven repositories, it was supposed read maven-metadata.xml first, but
because sbt customizes the repository layout for cross building, it has been falling back
to screen scraping of the Apache directory listing.
This problem surfaced as:

  • Version range not working for artifacts hosted on Bintray. #​2005
  • Potentially other SNAPSHOT related issues.

sbt 0.13.9 fixes this by relaxing the Maven compatiblity check, so it will read maven-metadata.xml. #​2075 by @​eed3si9n

Contributors

Special thanks to the contributors for making this release a success. Compared to 0.13.8, there were 127 (non-merge) commits, by 14 contributors: Eugene Yokota, Dale Wijnand, Josh Suereth, Andrew Johnson, David Perez, Matthew Farwell, Antonio Cunei, Andrzej Jozwik, James Roper, Vitalii Voloshyn, Benjy, Kamil Kloch, Max Worgan, Andreas Flierl. Thank you!

v0.13.8: 0.13.8

Compare Source

Changes with compatibility implications
  • Disable publishing on implicitly created root project by not enabling IvyPlugin by default (-Dsbt.root.ivyplugin=true will revert this behavior). #​1871/#​1869 by @​dwijnand
  • Rolls back XML parsing workaround. See below.
  • Enables cross-version support for Scala sources. See below.
Improvements
  • Adds Maven resolver plugin. See below.
  • Adds project-level dependency exclusions. See below.
  • Adds sequential tasks. See below.
  • Discovered main classes will be sorted. #​1180 by @​kretes
  • Implemented a new mechanism of forking javac, whereby errors are captured. Also more likely to run in-process. #​1702 by @​jsuereth
  • evicted will display all evictions (including the ones not suspected of binary incompatibility). #​1615 by @​eed3si9n
  • Better abstration to track new kinds of dependencies for incremental compiler. #​1340 by @​Duhemm
  • Source dependency uses --depth 1 for git clone. #​1787 by @​xuwei-k
  • Facilitate nicer ways of declaring project settings. See below. #​1902 by @​dwijnand
Fixes
Rolling back XML parsing workaround

sbt 0.13.7 implemented natural whitespace handling by switching build.sbt parsing to use Scala compiler, instead of blank line delimiting. We realized that some build definitions no longer parsed due to the difference in XML handlin

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants