sanity-plugin-taxonomy-manager 1.0.4 → 1.0.5

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.
package/CHANGELOG.md CHANGED
@@ -6,6 +6,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
6
6
 
7
7
  <!-- ## [TODO] -->
8
8
 
9
+ ## [1.0.5] - 2022-11-23
10
+ ### Fixed
11
+ - README link that was not behaving as intended across applications.
12
+
9
13
  ## [1.0.4] - 2022-10-20
10
14
  ### Fixed
11
15
  - Taxonomy Tree CSS was spilling over into description fields for the studio. Added unique classes to keep plugin styling from being too enterprising.
@@ -71,4 +75,24 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
71
75
  - Keep at the top to track upcoming changes.
72
76
  - People can see what changes they might expect in upcoming releases
73
77
  - At release time, you can move the Unreleased section changes into a new release version section.
78
+
79
+ ### Release Process
80
+ 1. Safety Checks:
81
+ - git pull
82
+ - git status
83
+ - npm ci
84
+ - npm test
85
+ 2. Prepare the Release:
86
+ - npm run build
87
+ 3. Update the Changelog
88
+ 4. Update the Version Number:
89
+ - npm version patch | minor | major -m "message"
90
+ 5. Publish to npm:
91
+ - npm publish
92
+ 6. Publish to Git:
93
+ - git push
94
+ - git push --tags
95
+ 7. Create a GitHub Release (optional)
96
+
97
+ source: https://cloudfour.com/thinks/how-to-publish-an-updated-version-of-an-npm-package/
74
98
  --->
package/README.md CHANGED
@@ -28,7 +28,7 @@ Standard optional SKOS documentation fields are included by default.
28
28
 
29
29
  ### Support for Single or Multiple Taxonomy Schemes (or none)
30
30
 
31
- For cases where more than one taxonomy is needed, multiple [SKOS Concept Schemes](https://www.w3.org/TR/skos-reference/#schemes) are supported. Schemes can be used to configure filtered views of concepts in [Sanity Structure Builder](https://www.sanity.io/docs/structure-builder-introduction), and will provide for additional filtering and view options in [future versions of Taxonomy Manager](#to-do).
31
+ For cases where more than one taxonomy is needed, multiple [SKOS Concept Schemes](https://www.w3.org/TR/skos-reference/#schemes) are supported. Schemes can be used to configure filtered views of concepts in [Sanity Structure Builder](https://www.sanity.io/docs/structure-builder-introduction), and will provide for additional filtering and view options in [future versions of Taxonomy Manager](README.md#to-do).
32
32
 
33
33
  <img src="https://user-images.githubusercontent.com/3710835/173248197-afcd1718-8aaa-4925-b2ea-f21f1a16a497.png" width="700">
34
34
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "sanity-plugin-taxonomy-manager",
3
- "version": "1.0.4",
3
+ "version": "1.0.5",
4
4
  "description": "Create and manage SKOS compliant taxonomies, thesauri, and classification schemes in Sanity Studio.",
5
5
  "scripts": {
6
6
  "lint": "eslint .",