@eeacms/volto-slate-footnote 6.1.5 → 6.1.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.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,21 @@ All notable changes to this project will be documented in this file. Dates are d
4
4
 
5
5
  Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).
6
6
 
7
+ ### [6.1.7](https://github.com/eea/volto-slate-footnote/compare/6.1.6...6.1.7) - 16 October 2023
8
+
9
+ #### :house: Internal changes
10
+
11
+ - chore:volto 16 in tests, update docs, fix stylelint overrides [valentinab25 - [`0fba06c`](https://github.com/eea/volto-slate-footnote/commit/0fba06c2977dec0d275d9c1969b738f2cfb278b2)]
12
+
13
+ #### :hammer_and_wrench: Others
14
+
15
+ - Update README [Cretu Mihaela - [`4fb3ce8`](https://github.com/eea/volto-slate-footnote/commit/4fb3ce890ec553fe6f51774b637292a98c836d93)]
16
+ ### [6.1.6](https://github.com/eea/volto-slate-footnote/compare/6.1.5...6.1.6) - 29 September 2023
17
+
18
+ #### :house: Documentation changes
19
+
20
+ - docs: Update README and DEVELOP [Alin Voinea - [`982fcbc`](https://github.com/eea/volto-slate-footnote/commit/982fcbc29cf82b428532138f948d9038b021b149)]
21
+
7
22
  ### [6.1.5](https://github.com/eea/volto-slate-footnote/compare/6.1.4...6.1.5) - 19 September 2023
8
23
 
9
24
  #### :bug: Bug Fixes
package/DEVELOP.md CHANGED
@@ -16,12 +16,14 @@
16
16
 
17
17
  1. Go to http://localhost:3000
18
18
 
19
- 1. Happy hacking!
19
+ 1. Initialize git hooks
20
20
 
21
21
  ```Bash
22
- cd src/addons/volto-slate-footnote/
22
+ yarn prepare
23
23
  ```
24
24
 
25
+ 1. Happy hacking!
26
+
25
27
  ### Or add @eeacms/volto-slate-footnote to your Volto project
26
28
 
27
29
  Before starting make sure your development environment is properly set. See [Volto Developer Documentation](https://docs.voltocms.com/getting-started/install/)
@@ -32,10 +34,7 @@ Before starting make sure your development environment is properly set. See [Vol
32
34
 
33
35
  1. Create new volto app
34
36
 
35
- yo @plone/volto my-volto-project \
36
- --workspace src/addons/volto-slate-footnote \
37
- --addon @eeacms/volto-slate-footnote \
38
- --skip-install
37
+ yo @plone/volto my-volto-project --addon @eeacms/volto-slate-footnote --skip-install
39
38
  cd my-volto-project
40
39
 
41
40
  1. Add the following to `mrs.developer.json`:
@@ -51,17 +50,15 @@ Before starting make sure your development environment is properly set. See [Vol
51
50
 
52
51
  1. Install
53
52
 
54
- yarn develop
53
+ make develop
55
54
  yarn
56
55
 
57
56
  1. Start backend
58
57
 
59
- docker run -d --name plone -p 8080:8080 -e SITE=Plone plone
58
+ docker run --pull always -it --rm --name plone -p 8080:8080 -e SITE=Plone plone/plone-backend
60
59
 
61
60
  ...wait for backend to setup and start - `Ready to handle requests`:
62
61
 
63
- docker logs -f plone
64
-
65
62
  ...you can also check http://localhost:8080/Plone
66
63
 
67
64
  1. Start frontend
package/Jenkinsfile CHANGED
@@ -6,7 +6,7 @@ pipeline {
6
6
  NAMESPACE = "@eeacms"
7
7
  SONARQUBE_TAGS = "volto.eea.europa.eu,biodiversity.europa.eu,www.eea.europa.eu-ims,climate-energy.eea.europa.eu,sustainability.eionet.europa.eu,forest.eea.europa.eu,clms.land.copernicus.eu,industry.eea.europa.eu,water.europa.eu-freshwater,demo-www.eea.europa.eu,clmsdemo.devel6cph.eea.europa.eu,water.europa.eu-marine,climate-adapt.eea.europa.eu,climate-advisory-board.devel4cph.eea.europa.eu,climate-advisory-board.europa.eu,www.eea.europa.eu-en"
8
8
  DEPENDENCIES = ""
9
- VOLTO = ""
9
+ VOLTO = "16"
10
10
  }
11
11
 
12
12
  stages {
@@ -41,19 +41,19 @@ pipeline {
41
41
 
42
42
  "ES lint": {
43
43
  node(label: 'docker') {
44
- sh '''docker run -i --rm --name="$BUILD_TAG-eslint" -e NAMESPACE="$NAMESPACE" -e VOLTO=$VOLTO -e GIT_NAME=$GIT_NAME -e GIT_BRANCH="$BRANCH_NAME" -e GIT_CHANGE_ID="$CHANGE_ID" plone/volto-addon-ci eslint'''
44
+ sh '''docker run -i --rm --name="$BUILD_TAG-eslint" -e NAMESPACE="$NAMESPACE" -e VOLTO=$VOLTO -e GIT_NAME=$GIT_NAME -e GIT_BRANCH="$BRANCH_NAME" -e GIT_CHANGE_ID="$CHANGE_ID" -e VOLTO=$VOLTO plone/volto-addon-ci eslint'''
45
45
  }
46
46
  },
47
47
 
48
48
  "Style lint": {
49
49
  node(label: 'docker') {
50
- sh '''docker run -i --rm --name="$BUILD_TAG-stylelint" -e NAMESPACE="$NAMESPACE" -e VOLTO=$VOLTO -e GIT_NAME=$GIT_NAME -e GIT_BRANCH="$BRANCH_NAME" -e GIT_CHANGE_ID="$CHANGE_ID" plone/volto-addon-ci stylelint'''
50
+ sh '''docker run -i --rm --name="$BUILD_TAG-stylelint" -e NAMESPACE="$NAMESPACE" -e VOLTO=$VOLTO -e GIT_NAME=$GIT_NAME -e GIT_BRANCH="$BRANCH_NAME" -e GIT_CHANGE_ID="$CHANGE_ID" -e VOLTO=$VOLTO plone/volto-addon-ci stylelint'''
51
51
  }
52
52
  },
53
53
 
54
54
  "Prettier": {
55
55
  node(label: 'docker') {
56
- sh '''docker run -i --rm --name="$BUILD_TAG-prettier" -e VOLTO=$VOLTO -e NAMESPACE="$NAMESPACE" -e GIT_NAME=$GIT_NAME -e GIT_BRANCH="$BRANCH_NAME" -e GIT_CHANGE_ID="$CHANGE_ID" plone/volto-addon-ci prettier'''
56
+ sh '''docker run -i --rm --name="$BUILD_TAG-prettier" -e VOLTO=$VOLTO -e NAMESPACE="$NAMESPACE" -e GIT_NAME=$GIT_NAME -e GIT_BRANCH="$BRANCH_NAME" -e GIT_CHANGE_ID="$CHANGE_ID" -e VOLTO=$VOLTO plone/volto-addon-ci prettier'''
57
57
  }
58
58
  }
59
59
  )
package/Makefile CHANGED
@@ -97,12 +97,12 @@ stylelint: ## Stylelint
97
97
 
98
98
  .PHONY: stylelint-overrides
99
99
  stylelint-overrides:
100
- $(NODE_MODULES)/.bin/stylelint --syntax less --allow-empty-input 'theme/**/*.overrides' 'src/**/*.overrides'
100
+ $(NODE_MODULES)/.bin/stylelint --custom-syntax less --allow-empty-input 'theme/**/*.overrides' 'src/**/*.overrides'
101
101
 
102
102
  .PHONY: stylelint-fix
103
103
  stylelint-fix: ## Fix stylelint
104
104
  $(NODE_MODULES)/stylelint/bin/stylelint.js --allow-empty-input 'src/**/*.{css,less}' --fix
105
- $(NODE_MODULES)/.bin/stylelint --syntax less --allow-empty-input 'theme/**/*.overrides' 'src/**/*.overrides' --fix
105
+ $(NODE_MODULES)/.bin/stylelint --custom-syntax less --allow-empty-input 'theme/**/*.overrides' 'src/**/*.overrides' --fix
106
106
 
107
107
  .PHONY: prettier
108
108
  prettier: ## Prettier
package/README.md CHANGED
@@ -21,7 +21,7 @@
21
21
 
22
22
  ### Easily annotate text within [Volto Slate](https://6.dev-docs.plone.org/volto/configuration/volto-slate/) text editor
23
23
 
24
- ![Insert footnotes](https://github.com/eea/volto-slate-footnote/raw/docs/docs/volto-slate-footnote.gif)
24
+ ![Insert footnotes](https://github.com/eea/volto-slate-footnote/raw/master/docs/volto-slate-footnote.gif)
25
25
 
26
26
  ## Upgrade
27
27
 
@@ -44,25 +44,25 @@ Go to http://localhost:3000
44
44
 
45
45
  1. Make sure you have a [Plone backend](https://plone.org/download) up-and-running at http://localhost:8080/Plone
46
46
 
47
- ```Bash
48
- docker compose up backend
49
- ```
47
+ ```Bash
48
+ docker compose up backend
49
+ ```
50
50
 
51
51
  1. Start Volto frontend
52
52
 
53
- - If you already have a volto project, just update `package.json`:
53
+ * If you already have a volto project, just update `package.json`:
54
54
 
55
55
  ```JSON
56
56
  "addons": [
57
- "@eeacms/volto-slate-footnote"
57
+ "@eeacms/volto-slate-footnote"
58
58
  ],
59
59
 
60
60
  "dependencies": {
61
- "@eeacms/volto-slate-footnote": "*"
61
+ "@eeacms/volto-slate-footnote": "*"
62
62
  }
63
63
  ```
64
64
 
65
- 1. If not, create one:
65
+ * If not, create one:
66
66
 
67
67
  ```
68
68
  npm install -g yo @plone/generator-volto
@@ -70,7 +70,6 @@ Go to http://localhost:3000
70
70
  cd my-volto-project
71
71
  ```
72
72
 
73
-
74
73
  1. Install new add-ons and restart Volto:
75
74
 
76
75
  ```
package/RELEASE.md CHANGED
@@ -20,9 +20,9 @@ You need to first install the [release-it](https://github.com/release-it/release
20
20
  ```
21
21
  npm install -g release-it
22
22
  ```
23
-
23
+
24
24
  Release-it uses the configuration written in the [`.release-it.json`](./.release-it.json) file located in the root of the repository.
25
-
25
+
26
26
  Release-it is a tool that automates 4 important steps in the release process:
27
27
 
28
28
  1. Version increase in `package.json` ( increased from the current version in `package.json`)
@@ -30,45 +30,45 @@ Release-it is a tool that automates 4 important steps in the release process:
30
30
  3. GitHub release on the commit with the changelog and package.json modification on the develop branch
31
31
  4. NPM release ( by default it's disabled, but can be enabled in the configuration file )
32
32
 
33
- To configure the authentification, you need to export GITHUB_TOKEN for [GitHub](https://github.com/settings/tokens)
33
+ To configure the authentification, you need to export GITHUB_TOKEN for [GitHub](https://github.com/settings/tokens)
34
34
 
35
35
  ```
36
36
  export GITHUB_TOKEN=XXX-XXXXXXXXXXXXXXXXXXXXXX
37
37
  ```
38
-
38
+
39
39
  To configure npm, you can use the `npm login` command or use a configuration file with a TOKEN :
40
-
40
+
41
41
  ```
42
42
  echo "//registry.npmjs.org/:_authToken=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYY" > .npmrc
43
43
  ```
44
44
 
45
45
  #### Using release-it tool
46
-
46
+
47
47
  There are 3 yarn scripts that can be run to do the release
48
48
 
49
49
  ##### yarn release-beta
50
50
 
51
- Automatically calculates and presents 3 beta versions - patch, minor and major for you to choose ( or Other for manual input).
51
+ Automatically calculates and presents 3 beta versions - patch, minor and major for you to choose ( or Other for manual input).
52
52
 
53
53
  ```
54
- ? Select increment (next version):
55
- ❯ prepatch (0.1.1-beta.0)
56
- preminor (0.2.0-beta.0)
57
- premajor (1.0.0-beta.0)
58
- Other, please specify...
54
+ ? Select increment (next version):
55
+ ❯ prepatch (0.1.1-beta.0)
56
+ preminor (0.2.0-beta.0)
57
+ premajor (1.0.0-beta.0)
58
+ Other, please specify...
59
59
  ```
60
60
 
61
61
  ##### yarn release-major-beta
62
62
 
63
63
  Same as `yarn release-beta`, but with premajor version pre-selected.
64
-
64
+
65
65
  ##### yarn release
66
66
 
67
67
  Generic command, does not automatically add the `beta` to version, but you can still manually write it if you choose Other.
68
68
 
69
69
  #### Important notes
70
70
 
71
- > Do not use release-it tool on master branch, the commit on CHANGELOG.md file and the version increase in the package.json file can't be done without a PULL REQUEST.
71
+ > Do not use release-it tool on master branch, the commit on CHANGELOG.md file and the version increase in the package.json file can't be done without a PULL REQUEST.
72
72
 
73
73
  > Do not keep Pull Requests from develop to master branches open when you are doing beta releases from the develop branch. As long as a PR to master is open, an automatic script will run on every commit and will update both the version and the changelog to a production-ready state - ( MAJOR.MINOR.PATCH mandatory format for version).
74
74
 
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@eeacms/volto-slate-footnote",
3
- "version": "6.1.5",
3
+ "version": "6.1.7",
4
4
  "description": "volto-slate-footnote: Volto add-on",
5
5
  "main": "src/index.js",
6
6
  "author": "European Environment Agency: IDM2 A-Team",