@diesdasdigital/linting - npm Package Compare versions

Comparing version 2.0.2 to 2.0.3

package.json

 {
   "name": "@diesdasdigital/linting",
-  "version": "2.0.2",
+  "version": "2.0.3",
   "description": "Stylelint config default for Diesdas internal projects",
@@ -5,0 +5,0 @@ "main": "stylelint-config.js",

README.md

@@ -43,1 +43,14 @@ # `@diesdasdigital/linting`
 You're done!
+
+# Package Maintenance
+
+## Releasing a new version
+
+This project uses the
+[`npm-publish-action`](https://github.com/pascalgn/npm-publish-action) to
+automatically publish new releases to NPM and tag them on Github. To trigger a
+new release, then commit a change to the `version` number in `package.json` with
+the commit message `Release x.x.x` (but replace `x.x.x` with the new version
+number). Push the commit to `origin/main` and then view the status of the
+automated release
+[here](https://github.com/diesdasdigital/linting/actions?query=workflow%3Anpm-publish).

stylelint-config.js

@@ -76,5 +76,5 @@ module.exports = {
     "declaration-property-value-disallowed-list": {
-      outline: ["none", "0"],
+      outline: ["none", "0", "unset"],
     },
   },
 };

Fixed alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

10395

increased by5.82%

Number of lines in readme file

56

increased by30.23%

Number of medium supply chain risk alerts

0

decreased by-100%

No dependency changes