vega-datasets - npm Package Compare versions

Comparing version 2.2.0 to 2.2.1--canary.312.32a9ed7.0

build/package.json

@@ -20,5 +20,8 @@ {
     "devDependencies": {
+        "@auto-it/conventional-commits": "^10.32.0",
+        "@auto-it/first-time-contributor": "^10.32.0",
         "@rollup/plugin-json": "^4.1.0",
-        "@rollup/plugin-node-resolve": "^9.0.0",
-        "@types/d3-dsv": "^1.1.0",
+        "@rollup/plugin-node-resolve": "^13.0.0",
+        "@types/d3-dsv": "^2.0.0",
+        "auto": "^10.32.0",
         "d3-dsv": "^2.0.0",
@@ -36,4 +39,5 @@ "datalib": "^1.9.3",
         "flights": "node scripts/flights.js",
-        "github": "python scripts/github.py"
+        "github": "python scripts/github.py",
+        "release": "auto shipit"
     }
 }

package.json

 {
   "name": "vega-datasets",
-  "version": "2.2.0",
+  "version": "2.2.1--canary.312.32a9ed7.0",
   "description": "Common repository for example datasets used by Vega related projects.",
@@ -20,5 +20,8 @@ "license": "BSD-3-Clause",
   "devDependencies": {
+    "@auto-it/conventional-commits": "^10.32.0",
+    "@auto-it/first-time-contributor": "^10.32.0",
     "@rollup/plugin-json": "^4.1.0",
-    "@rollup/plugin-node-resolve": "^9.0.0",
-    "@types/d3-dsv": "^1.1.0",
+    "@rollup/plugin-node-resolve": "^13.0.0",
+    "@types/d3-dsv": "^2.0.0",
+    "auto": "^10.32.0",
     "d3-dsv": "^2.0.0",
@@ -36,4 +39,5 @@ "datalib": "^1.9.3",
     "flights": "node scripts/flights.js",
-    "github": "python scripts/github.py"
+    "github": "python scripts/github.py",
+    "release": "auto shipit"
   }
 }

README.md

@@ -11,3 +11,3 @@ # Vega Datasets
 
-The list of sources is in [SOURCES.md](https://github.com/vega/vega-datasets/blob/master/SOURCES.md).
+The list of sources is in [SOURCES.md](https://github.com/vega/vega-datasets/blob/next/SOURCES.md).
 
@@ -20,6 +20,14 @@ To access the data in Observable, you can import `vega-dataset`. Try our [example notebook](https://observablehq.com/@vega/vega-datasets). To access these datasets from Python, you can use the [Vega datasets python package](https://github.com/altair-viz/vega_datasets). To access them from Julia, you can use the [VegaDatasets.jl julia package](https://github.com/davidanthoff/VegaDatasets.jl).
 
-We do not change data in patch releases except to resolve formatting issues. Minor releases may change the data but only update datasets in ways that do not change field names or file names. Minor releases may also add datasets. Major versions may change file names, file contents, and remove or update files. 
+We do not change data in patch releases except to resolve formatting issues. Minor releases may change the data but only update datasets in ways that do not change field names or file names. Minor releases may also add datasets. Major versions may change file names, file contents, and remove or update files.
 
 ## How to use it
 
+### HTTP
+
+You can also get the data directly via HTTP served by GitHub or jsDelivr (a fast CDN) like:
+
+https://vega.github.io/vega-datasets/data/cars.json or with a fixed version (recommended) such as https://cdn.jsdelivr.net/npm/vega-datasets@2/data/cars.json.
+
+You can find a full listing of the available datasets at https://cdn.jsdelivr.net/npm/vega-datasets/data/.
+
 ### NPM
@@ -55,10 +63,13 @@
 
-### HTTP
+## Development process
 
-You can also get the data directly via HTTP served by GitHub or jsDelivr (a fast CDN) like:
+Install dependencies with `yarn`.
 
-https://vega.github.io/vega-datasets/data/cars.json or with a fixed version (recommended) such as https://cdn.jsdelivr.net/npm/vega-datasets@1.31/data/cars.json.
+## Release Process
 
-## Development process
+Publishing is handled by a 2-branch [pre-release process](https://intuit.github.io/auto/docs/generated/shipit#next-branch-default), configured in `publish.yml`. All changes should be based off the default `next` branch, and are published automatically.
 
-Install dependencies with `yarn`. To make a release, create a new tagged version with `yarn version` and then push the tag. The CI will automatically make a release. 
+- PRs made into the default branch that [would trigger a version bump](https://intuit.github.io/auto/docs/generated/conventional-commits) are auto-deployed to the `next` pre-release tag on NPM. The result can be installed with `npm install vega-datasets/@next`.
+  - When merging into `next`, please use the `squash and merge` strategy.
+- To release a new stable version, open a PR from `next` into `stable` using this [compare link](https://github.com/vega/vega-datasets/compare/stable...next).
+  - When merging from `next` into `stable`, please use the `create a merge commit` strategy.

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Number of lines in readme file

73

increased by17.74%

Number of medium supply chain risk alerts

3

decreased by-25%

Worsened metrics

Total package byte prevSize

33757828

decreased by-0.04%

Dev dependency count

11

increased by37.5%

Number of package files

80

decreased by-5.88%

Lines of code

165291

decreased by-0.11%

Number of low quality alerts

2

increased by100%

No dependency changes