unicode-property-aliases-ecmascript - npm Package Compare versions

Comparing version 1.1.0 to 2.0.0

package.json

 {
   "name": "unicode-property-aliases-ecmascript",
-  "version": "1.1.0",
+  "version": "2.0.0",
   "description": "Unicode property alias mappings in JavaScript format for property names that are supported in ECMAScript RegExp property escapes.",
@@ -37,3 +37,3 @@ "homepage": "https://github.com/mathiasbynens/unicode-property-aliases-ecmascript",
   "scripts": {
-    "download": "curl http://unicode.org/Public/13.0.0/ucd/PropertyAliases.txt > data/PropertyAliases.txt",
+    "download": "curl http://unicode.org/Public/14.0.0/ucd/PropertyAliases.txt > data/PropertyAliases.txt",
     "build": "node scripts/build.js",
@@ -40,0 +40,0 @@ "test": "ava tests/tests.js"

README.md

@@ -1,6 +0,6 @@
-# unicode-property-aliases-ecmascript [![Build status](https://travis-ci.org/mathiasbynens/unicode-property-aliases-ecmascript.svg?branch=master)](https://travis-ci.org/mathiasbynens/unicode-property-aliases-ecmascript)
+# unicode-property-aliases-ecmascript [![Build status](https://travis-ci.org/mathiasbynens/unicode-property-aliases-ecmascript.svg?branch=main)](https://travis-ci.org/mathiasbynens/unicode-property-aliases-ecmascript) [![unicode-property-aliases-ecmascript on npm](https://img.shields.io/npm/v/unicode-property-aliases-ecmascript)](https://www.npmjs.com/package/unicode-property-aliases-ecmascript)
 
 _unicode-property-aliases-ecmascript_ offers Unicode property alias mappings in an easy-to-consume JavaScript format. It only contains the Unicode property names that are supported in [ECMAScript RegExp property escapes](https://github.com/tc39/proposal-regexp-unicode-property-escapes).
 
-It’s based on [the `PropertyAliases.txt` data for Unicode v12.0.0](http://unicode.org/Public/12.0.0/ucd/PropertyAliases.txt).
+It’s based on Unicode’s `PropertyAliases.txt`.
 
@@ -30,2 +30,24 @@ ## Installation
 
+## For maintainers
+
+### How to publish a new release
+
+1. On the `main` branch, bump the version number in `package.json`:
+
+    ```sh
+    npm version patch -m 'Release v%s'
+    ```
+
+    Instead of `patch`, use `minor` or `major` [as needed](https://semver.org/).
+
+    Note that this produces a Git commit + tag.
+
+1. Push the release commit and tag:
+
+    ```sh
+    git push && git push --tags
+    ```
+
+    Our CI then automatically publishes the new release to npm.
+
 ## Author
@@ -32,0 +54,0 @@

New 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

5976

increased by10.48%

Number of lines in readme file

61

increased by56.41%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes