Skip to content

Releases: JuliaEcosystem/PackageAnalyzer.jl

v3.1.0

07 Dec 01:35
293a083
Compare
Choose a tag to compare

PackageAnalyzer v3.1.0

Diff since v3.0.1

Merged pull requests:

Closed issues:

  • Error while analysing Mads (#90)

v3.0.1

22 Jul 22:56
0c46d58
Compare
Choose a tag to compare

PackageAnalyzer v3.0.1

Diff since v2.0.0

Closed issues:

  • Docstrings count as code (#76)

Merged pull requests:

v2.0.0

11 Jun 13:01
8a3f34d
Compare
Choose a tag to compare

PackageAnalyzer v2.0.0

Diff since v1.0.0

Closed issues:

  • Registered version is very old (#75)
  • Register Julia 1.3 branch (#81)
  • Use Legolas.jl to define Package type? (#83)

Merged pull requests:

v0.2.0

26 Jan 13:35
Compare
Choose a tag to compare

PackageAnalyzer v0.2.0

Diff since v0.1.0

Closed issues:

  • Update dependencies to prevent environment-wide downgrades (#66)
  • Deal with compressed registry in Julia v1.7 (#67)
  • Analyze manifest (#70)
  • Is documention a typo ? (#73)
  • Registered version is very old (#75)
  • Register Julia 1.3 branch (#81)

Merged pull requests:

v1.0.0

24 Nov 13:54
f71ba76
Compare
Choose a tag to compare

PackageAnalyzer v1.0.0

Diff since v0.1.0

Closed issues:

  • Update dependencies to prevent environment-wide downgrades (#66)
  • Deal with compressed registry in Julia v1.7 (#67)
  • Analyze manifest (#70)
  • Is documention a typo ? (#73)

Merged pull requests:

v0.1.0

05 Jul 11:28
1a4f98b
Compare
Choose a tag to compare

PackageAnalyzer v0.1.0

Closed issues:

  • Look for license file (#4)
  • Reorganise the workflow (#5)
  • Count lines of code? (#8)
  • Subdirectory support (#10)
  • licensecheck fails on Knet (#14)
  • Naming bikeshedding (#20)
  • subdir issue (#28)
  • Copying a discussion from RegistryHealthChecks.jl (#36)
  • Update documentation about registering type with Arrow (#52)

Merged pull requests:

results-2021-03-22: Close STDIN to prevent git from prompting for username/password (#46)

23 Mar 00:01
37223fe
Compare
Choose a tag to compare
Also, make the test with the non-existing repo more robust: GitHub doesn't allow
`!` in repo names, so trying to clone `DOES_NOT_EXIST!!!.jl` would fail
immediately anyway.  Instead we want to test that trying to clone a repo with a
valid name doesn't prompt for username/password.

Report 2021-01-23

24 Jan 00:18
Compare
Choose a tag to compare

Data structure:

struct Package
    name::String # name of the package
    repo::String # URL of the repository
    reachable::Bool # can the repository be cloned?
    docs::Bool # does it have documentation?
    runtests::Bool # does it have the test/runtests.jl file?
    github_actions::Bool # does it use GitHub Actions?
    travis::Bool # does it use Travis CI?
    appveyor::Bool # does it use AppVeyor?
    cirrus::Bool # does it use Cirrus CI?
    circle::Bool # does it use Circle CI?
    drone::Bool # does it use Drone CI?
    buildkite::Bool # does it use Buildkite?
    azure_pipelines::Bool # does it use Azure Pipelines?
    gitlab_pipeline::Bool # does it use Gitlab Pipeline?
end

Revision of the General registry: JuliaRegistries/General@824e39a