pane-registry 2.4.6 → 2.4.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -5,9 +5,12 @@ name: CI
5
5
 
6
6
  on:
7
7
  push:
8
- branches: [ main ]
8
+ branches:
9
+ - "**"
9
10
  pull_request:
10
- branches: [ main ]
11
+ branches:
12
+ - "**"
13
+ workflow_dispatch:
11
14
 
12
15
  jobs:
13
16
  build:
@@ -16,8 +19,10 @@ jobs:
16
19
 
17
20
  strategy:
18
21
  matrix:
19
- node-version: [ 10.x, 12.x, 14.x, 15.x ]
20
- # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
22
+ node-version:
23
+ - 12.x
24
+ - 14.x
25
+ - 16.x
21
26
 
22
27
  steps:
23
28
  - uses: actions/checkout@v2
@@ -29,3 +34,31 @@ jobs:
29
34
  - run: npm run lint
30
35
  - run: npm test
31
36
  - run: npm run build --if-present
37
+ - name: Save build
38
+ if: matrix.node-version == '14.x'
39
+ uses: actions/upload-artifact@v2
40
+ with:
41
+ name: build
42
+ path: |
43
+ .
44
+ !node_modules
45
+ retention-days: 1
46
+ npm-publish-build:
47
+ needs: build
48
+ runs-on: ubuntu-latest
49
+ steps:
50
+ - uses: actions/download-artifact@v2
51
+ with:
52
+ name: build
53
+ - uses: actions/setup-node@v1
54
+ with:
55
+ node-version: 14.x
56
+ - uses: rlespinasse/github-slug-action@v3.x
57
+ - name: Append commit hash to package version
58
+ run: 'sed -i -E "s/(\"version\": *\"[^\"]+)/\1-${GITHUB_SHA_SHORT}/" package.json'
59
+ - name: Disable pre- and post-publish actions
60
+ run: 'sed -i -E "s/\"((pre|post)publish)/\"ignore:\1/" package.json'
61
+ - uses: JS-DevTools/npm-publish@v1
62
+ with:
63
+ token: ${{ secrets.NPM_TOKEN }}
64
+ tag: ${{ env.GITHUB_REF_SLUG }}
package/README.md CHANGED
@@ -4,4 +4,4 @@ An index to hold all loaded solid panes, whether statically or dynamically loade
4
4
 
5
5
  # Adendum
6
6
 
7
- The pane registry is a crucial part of the Solid Panes systerm. It is wherre any pane inserts itself or is inserted. In the standard working of solidOS, there is one place in solid-panes where all the nomal panes are loaded into the pane registry. But other apps, and especially developers developing new panes can insert their own panes. And so we hope we will end up with panes dynamically laoded according to user configuration preferences.
7
+ The pane registry is a crucial part of the Solid Panes system. It is where any pane inserts itself or is inserted. In the standard working of SolidOS, there is one place in solid-panes where all the normal panes are loaded into the pane registry (see: [registerPanes.js](https://github.com/solid/solid-panes/blob/main/src/registerPanes.js) in solid-panes). But other apps, and especially developers developing new panes can insert their own panes. And so we hope we will end up with panes dynamically laoded according to user configuration preferences.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pane-registry",
3
- "version": "2.4.6",
3
+ "version": "2.4.7",
4
4
  "description": "Solid-compatible Panes: Pane Registry",
5
5
  "main": "./paneRegistry.js",
6
6
  "types": "./index.d.ts",
@@ -38,7 +38,7 @@
38
38
  "homepage": "https://github.com/solid/chat-pane",
39
39
  "dependencies": {
40
40
  "rdflib": "^2.2.17",
41
- "solid-logic": "^1.3.13"
41
+ "solid-logic": "^1.3.14"
42
42
  },
43
43
  "devDependencies": {
44
44
  "eslint": "^7.32.0",