splainer-search - npm Package Compare versions

Comparing version 2.20.1 to 2.20.2

CHANGELOG.md

 Version numbers correspond to `package.json` version.  Follows the _major.minor.bugfix_ naming pattern as of 2.8.0.
 
+# 2.20.2 (2023-04-28)
+- Urls that link to a individual document in OpenSearch and ES7+ have changed to have a `_doc` element in the path.  https://github.com/o19s/splainer-search/pull/117 by @mkr fixes https://github.com/o19s/quepid/issues/701.
+
+- `npm outdated` highlights nothings.  All dependencies (barring this is Angular 1 ;-) ) are up to date.  https://github.com/o19s/splainer-search/pull/118 by @epugh.
+
 # 2.20.0 (2022-10-13)
@@ -39,3 +44,3 @@ - We now support API keys!  Search engine deploys (like Elastic Cloud) are increasingly locked down, with an API Key being the most common way to access them.  Splainer-search now supports custom headers, which supports the api key usecase, and lays ground work for other use cases.   A huge round of thanks goes to @aditya-kanekar who created the first implmentation via https://github.com/o19s/splainer-search/pull/116, and then @worleydl for making it more generic.   This improvement will be surfaced into [Splainer](http://splainer.io) and [Quepid](http://quepid.com) asap.
 # 2.12.0 (2021-12-17)
-- Links to individual Documents generated for Solr search engines (`doc._url()`) have faceting turned on for ALL of the fields listed.  This may be a feature to help you understand about a single document, however I don't quite have a use case that makes sense.  @jeffryedvm showed me it taking 30 seconds to query a single Solr doc due to what was blindly being faceted on, and opened https://github.com/o19s/quepid/issues/442.  
+- Links to individual Documents generated for Solr search engines (`doc._url()`) have faceting turned on for ALL of the fields listed.  This may be a feature to help you understand about a single document, however I don't quite have a use case that makes sense.  @jeffryedvm showed me it taking 30 seconds to query a single Solr doc due to what was blindly being faceted on, and opened https://github.com/o19s/quepid/issues/442.
 
@@ -42,0 +47,0 @@

package.json

 {
   "name": "splainer-search",
-  "version": "2.20.1",
+  "version": "2.20.2",
   "main": "splainer-search.js",
@@ -55,6 +55,6 @@ "authors": [
     "karma-jasmine": "^5.1.0",
-    "puppeteer": "^18.0.2"
+    "puppeteer": "^19.0.0"
   },
   "engines": {
-    "node": ">=14"
+    "node": ">=16"
   },
@@ -61,0 +61,0 @@ "scripts": {

README.md

@@ -327,7 +327,12 @@ [![Build Status](https://travis-ci.org/o19s/splainer-search.svg?branch=master)](https://travis-ci.org/o19s/splainer-search)
 ```
+### Release Process
 
-We use NP to publish splainer-search to npmjs.org.  You need to update the
+We use NP to publish splainer-search to npmjs.org.  
+
+1. You need to update the
 `CHANGELOG.md` with your new version and the date, but you don't need to touch `package.json`,
-the `np` script bumps that file!
+the `np` script bumps that file!   Check that file in.
 
+2. Now install the 'np' script if you don't have it, and run it to create the release:
+
 ```
@@ -338,3 +343,4 @@ npm install --global np
 
-This will also pop open a browser window on GitHub to create a new release for the project.
+3. This will also pop open a browser window on GitHub to create a new release for the project.
+Use the "Generate Release Notes" button on Github to make the template, and then paste in the contents of `CHANGELOG.md` into the _Whats Changed_ section.
 
@@ -341,0 +347,0 @@

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

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

Total package byte prevSize

155512

increased by0.47%

Number of lines in readme file

351

increased by1.74%

No dependency changes