Compare commits

...

6 Commits

Author SHA1 Message Date
Daniel Waxweiler 82800a9db3 clarify two steps in release procedure 2024-04-06 08:27:24 +02:00
Daniel Waxweiler 46170377af prepare next release 2024-04-06 08:25:16 +02:00
Daniel Waxweiler 5c1a186456 release version 1.0.0 2024-04-06 08:22:26 +02:00
Daniel Waxweiler 7a0075e5ed clarify features 2024-04-06 07:50:47 +02:00
Daniel Waxweiler 392d552dab npm audit fix 2024-04-06 07:42:42 +02:00
Daniel Waxweiler 797a08cfb6 update dev dependencies 2024-04-06 07:41:15 +02:00
7 changed files with 2132 additions and 1257 deletions

View File

@ -1,5 +1,2 @@
#!/bin/sh
. "$(dirname "$0")/_/husky.sh"
npm test
npx lint-staged

View File

@ -22,21 +22,23 @@ The current changelog can be found under [source/changelog.txt](source/changelog
### Release procedure
1. Make sure `changelog.txt` is up-to-date.
2. Use a new version number and copy over the new section into `readme.txt`.
3. Update `package.json` with the same version number.
4. Update the `package-lock.json`: `npm i --package-lock-only`
5. Build: `npm run build-prod`
6. Make sure screenshots are up-to-date.
7. Copy the built plugin into `/trunk` of SVN.
8. Create a new tag of the new version: `svn cp trunk tags/<version>`
9. Check the version number occurrences in both folders.
10. Commit everything together to the release SVN: `svn ci -m "release version <version>"` Make sure to add new files beforehand.
11. Commit the new version in git with the same message.
12. Tag the new version: `git tag v<version>`
13. Push the new tag to the repository: `git push --tags`
14. Append `-next` to the version number in `package.json`.
15. Update the `package-lock.json`: `npm i --package-lock-only`
16. Commit: `git commit -am "prepare next release"`
2. Create a new section with a new version number.
3. Copy over the new section into `readme.txt`.
4. Update `package.json` with the same version number.
5. Update the `package-lock.json`: `npm i --package-lock-only`
6. Build: `npm run build-prod`
7. Make sure screenshots are up-to-date.
8. Copy the built plugin into `/trunk` of SVN.
9. Create a new tag of the new version: `svn cp trunk tags/<version>`
10. Check the version number occurrences in both folders.
11. Make sure to handle exclamation and question marks in `svn status`.
12. Commit everything together to the release SVN: `svn ci -m "release version <version>"`
13. Commit the new version in git with the same message.
14. Tag the new version: `git tag v<version>`
15. Push the new tag to the repository: `git push --tags`
16. Append `-next` to the version number in `package.json`.
17. Update the `package-lock.json`: `npm i --package-lock-only`
18. Commit: `git commit -am "prepare next release"`
### Other commands

Binary file not shown.

Before

Width:  |  Height:  |  Size: 60 KiB

After

Width:  |  Height:  |  Size: 76 KiB

3318
package-lock.json generated

File diff suppressed because it is too large Load Diff

View File

@ -1,6 +1,6 @@
{
"name": "connector-mobilizon",
"version": "0.11.5-next",
"version": "1.0.0-next",
"description": "Display Mobilizon events in WordPress.",
"private": true,
"type": "module",
@ -11,7 +11,7 @@
"coverage": "c8 --all --reporter=html --reporter=text --include=source/**/*.js ava",
"eslint": "npx eslint source/**/*.js",
"format": "npx prettier --write .",
"prepare": "husky install",
"prepare": "husky",
"test": "ava && ./vendor/bin/phpunit"
},
"author": {
@ -32,11 +32,11 @@
"@babel/eslint-parser": "7.24.1",
"@babel/preset-env": "7.24.4",
"@babel/preset-react": "7.24.1",
"@wordpress/eslint-plugin": "17.2.0",
"ava": "5.3.1",
"@wordpress/eslint-plugin": "17.12.0",
"ava": "6.1.2",
"babel-loader": "9.1.3",
"browser-env": "3.3.0",
"c8": "8.0.1",
"c8": "9.1.0",
"copy-webpack-plugin": "12.0.2",
"eslint": "8.57.0",
"eslint-plugin-ava": "14.0.0",
@ -45,7 +45,7 @@
"esm": "3.2.25",
"gulp": "4.0.2",
"gulp-replace": "1.1.4",
"husky": "8.0.3",
"husky": "9.0.11",
"lint-staged": "15.2.2",
"prettier": "3.2.5",
"rimraf": "5.0.5",

View File

@ -1,14 +1,19 @@
### [Unreleased]
#### Added
#### Changed
#### Deprecated
#### Removed
#### Fixed
#### Security
### [1.0.0]
#### Added
- Display name of group when it cannot be found
#### Changed
- Let backend do requests to API of Mobilizon instance for increased privacy
- Update dependencies
#### Deprecated
#### Removed
#### Fixed
- Fix displaying more than one block in the editor
#### Security
### [0.11.5]
#### Changed

View File

@ -16,10 +16,10 @@ License: <wordpress-license>
Features
- Display events as Gutenberg block, as widget and as shortcut
- Display events' title, date, and location, if available
- Display events' title with link, date, and location, if available
- Cache requests' responses for 2 minutes in the database
- Configure number of events to show per block, per widget and per shortcut
- Optionally filter events by a specific group per block, per widget and per shortcut
- Optionally filter events by a specific public group per block, per widget and per shortcut
- Set the URL of the Mobilizon instance in the settings
- Toggle adding named offset in brackets after the time in the settings
@ -41,6 +41,15 @@ You have to use their username, e.g. `@nosliensvivants`, and append the name of
## Changelog
### [1.0.0]
#### Added
- Display name of group when it cannot be found
#### Changed
- Let backend do requests to API of Mobilizon instance for increased privacy
- Update dependencies
#### Fixed
- Fix displaying more than one block in the editor
### [0.11.5]
#### Changed
- Confirm compatibility with WordPress 6.5