Prepare for 1.8.1 Release

[barrettk]

Changeset: https://github.com/metrumresearchgroup/bbr/compare/1.8.0...release/1.8.1

[barrettk]

Scorecard Details

[barrettk]

@kyleam I ran with these args:

score-r-pkg --allow-untagged --pkgr-repos-pre=https://s3.amazonaws.com/mpn.metworx.dev/releases/nmrec/0.3.0 ~/data/Projects/package_dev/pkg-val-artifacts

The full table looked like this:

However, I was also surprised to see it change from 1.8.0. Perhaps some tests were skipped on my end?

[kyleam]

@kyleam I ran with these args:

Ah, perfect, so it's not that.

However, I was also surprised to see it change from 1.8.0. Perhaps some tests were skipped on my end?

I think it's just a matter of the bbi version, then. I'm running with v3.3.0. I suspect the numbers you're reporting for this PR are with a version before 3.2.0 (perhaps 3.1.1, which ships with the current Metworx).

In terms of the difference with what you reported in gh-633, could you have been using a newer bbi version for that?

(This is all speculation; I'll confirm that I see the same numbers when I run with bbi 3.1.1.)

[kyleam]

I'll confirm that I see the same numbers when I run with bbi 3.1.1

Confirmed that I get the same coverage as you with that bbi version:

[...]
scores:
{
  "testing": {
    "check": 1,
    "covr": 0.8353
  },
  "documentation": {
    "has_vignettes": 1,
    "has_website": 1,
    "has_news": 1
  },
  "maintenance": {
    "has_maintainer": 1,
    "news_current": 1
  },
  "transparency": {
    "has_source_control": 1,
    "has_bug_reports_url": 1
  }
}

$ bbi version
v3.1.1

The file-level values from the table also line up.