From fc625aa3a9b36a0634dfcb2d604ee33762b539c4 Mon Sep 17 00:00:00 2001 From: Michiel Devriese Date: Fri, 8 Sep 2023 12:23:31 +0200 Subject: [PATCH 1/4] Create a new tag when `package.json` is updated with a new version --- .github/workflows/create-tag.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 .github/workflows/create-tag.yaml diff --git a/.github/workflows/create-tag.yaml b/.github/workflows/create-tag.yaml new file mode 100644 index 000000000..bae3aaf38 --- /dev/null +++ b/.github/workflows/create-tag.yaml @@ -0,0 +1,13 @@ +--- +name: Create new tag + +on: + push: + branches: + - next-release + paths: + - "package.json" +jobs: + create-new-tag: + uses: teamleadercrm/teamleader-github-workflows/.github/workflows/create-tag-node.yaml@v1.13 + secrets: inherit From 9e936e179a644c661b95996bf71469fb238cf1f2 Mon Sep 17 00:00:00 2001 From: Michiel Devriese Date: Fri, 8 Sep 2023 12:25:13 +0200 Subject: [PATCH 2/4] Update readme --- README.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/README.md b/README.md index 1229aebec..9503448ac 100644 --- a/README.md +++ b/README.md @@ -107,11 +107,7 @@ $ PORT=3001 yarn start ``` 4. Once the pull request has the needed amount of approvals, merge it into the `next-release` branch. -5. Publish a `release` on Github and fill in the following fields: - - **Tag version:** `new.version.number` @ `target: next-release` - - **Release title:** `new.version.number` - - **Description:** add the `changelog items` -6. In your `console`, pull the `next-release` branch. +5. Github Actions will create a tag + release 7. `Publish` to `npm` using the `npm publish --access=public` command. 8. `Merge` the `next-release` branch into `master` and push to Github From ef091b58f0e98c490d525ed53b4460fbbf61f44b Mon Sep 17 00:00:00 2001 From: Michiel Devriese Date: Fri, 8 Sep 2023 12:32:32 +0200 Subject: [PATCH 3/4] Reintroduce step 6 --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 9503448ac..f5caa4935 100644 --- a/README.md +++ b/README.md @@ -108,6 +108,7 @@ $ PORT=3001 yarn start 4. Once the pull request has the needed amount of approvals, merge it into the `next-release` branch. 5. Github Actions will create a tag + release +6. In your `console`, pull the `next-release` branch. 7. `Publish` to `npm` using the `npm publish --access=public` command. 8. `Merge` the `next-release` branch into `master` and push to Github From 159aa2c28e6023eeebc6129b700d3d463db1a68c Mon Sep 17 00:00:00 2001 From: Michiel Devriese Date: Fri, 8 Sep 2023 12:33:19 +0200 Subject: [PATCH 4/4] Expand readme information about releases --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f5caa4935..68c73b4d1 100644 --- a/README.md +++ b/README.md @@ -107,7 +107,7 @@ $ PORT=3001 yarn start ``` 4. Once the pull request has the needed amount of approvals, merge it into the `next-release` branch. -5. Github Actions will create a tag + release +5. Github Actions will create a tag + release based on the `version` property in `package.json` 6. In your `console`, pull the `next-release` branch. 7. `Publish` to `npm` using the `npm publish --access=public` command. 8. `Merge` the `next-release` branch into `master` and push to Github