Skip to content

Commit 94b3444

Browse files
authored
Merge pull request #25 from GuiLeme/ci-set-version
ci: added script to set manifest version along with tagging.
2 parents 2298c21 + 2e23705 commit 94b3444

5 files changed

Lines changed: 884 additions & 477 deletions

File tree

.github/workflows/publish-tag.yml

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,12 @@ jobs:
3838
- name: Bump version and push tag
3939
run: |
4040
npm install
41-
npm version ${{ github.event.inputs.release_type }} -m "chore: bump version to %s"
41+
npm version ${{ github.event.inputs.release_type }} --no-git-tag-version
42+
NEW_VERSION=$(node -e "console.log(require('./package.json').version)")
43+
npm run set-manifest:version -- "$NEW_VERSION"
44+
git add package.json package-lock.json manifest.json
45+
git commit -m "chore: bump version to $NEW_VERSION"
46+
git tag "v$NEW_VERSION"
4247
git push --follow-tags
4348
env:
4449
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

README.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,22 @@ pluginManifests=[{"url":"<your-domain>/path/to/manifest.json"}]
2727
Or additionally, you can add this same configuration in the `.properties` file from `bbb-web` in `/usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties`
2828

2929

30+
## Setting the Plugin manifest Version
31+
32+
To set or update the `version` field in `manifest.json`, run:
33+
34+
```bash
35+
npm run set-manifest:version -- <version>
36+
```
37+
38+
For example:
39+
40+
```bash
41+
npm run set-manifest:version -- 1.0.0
42+
```
43+
44+
This will add the field if it doesn't exist yet, or overwrite it if it does.
45+
3046
## Development mode
3147

3248
As for development mode (running this plugin from source), please, refer back to https://github.com/bigbluebutton/bigbluebutton-html-plugin-sdk section `Running the Plugin from Source`

0 commit comments

Comments
 (0)