chore: automate github release for server

wkillerud · Oct 6, 2024 · fceab7f · fceab7f
1 parent 01d4c58
commit fceab7f
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 3 deletions.
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -63,3 +63,11 @@ jobs:
           NPM_CONFIG_PROVENANCE: true
           VSCE_PAT: ${{ secrets.VSCE_PAT }}
           OVSX_PAT: ${{ secrets.OVSX_PAT }}
+
+      - name: Release
+        uses: softprops/action-gh-release@v2
+        with:
+          generate_release_notes: true
+          make_latest: false
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/docs/src/contributing/releases.md b/docs/src/contributing/releases.md
@@ -19,7 +19,7 @@ nx reads the commit messages to determine what the new version should be, and to
 | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `docs: add guide for configuring sublime`                                                                                                 | No new release.                                                                                                                                                      |
 | `fix: update css-languageservice`                                                                                                         | Patch. Bugfix release, updates for runtime dependencies.                                                                                                             |
-| `feat: add support for show keyword in forward`                                                                                           | Minor. New feature release.                                                                                                                                          |
+| `feat: add support for show keyword in fo÷rward`                                                                                           | Minor. New feature release.                                                                                                                                          |
 | `refactor: remove reduntant options for latest language version`<br><br>`BREAKING CHANGE: The scanImportedFiles option has been removed.` | Major. Breaking release, like removing an option or changing `engines` version. <br /> (Note that the `BREAKING CHANGE: ` token must be in the footer of the commit) |
 
 ## Release process
@@ -31,7 +31,7 @@ To start a new release, run `node .scripts/release.mjs`. This script:
 3. Runs `npm run release` which updates versions, generates changelogs and Git tags.
 4. Pushes the changes and tags with `git push && git push --tags`.
 
-GitHub Actions does the actual publishing when there are new tags.  Create a [new GitHub release](https://github.com/wkillerud/some-sass/releases/[email protected]) for the latest tag.
+GitHub Actions does the actual publishing when there are new tags.
 
 The script continues to:
 
@@ -41,7 +41,7 @@ The script continues to:
 4. Commit the changes and run `git tag some-sass@<version from package.json>`.
 5. Run `git push && git push --tags`.
 
-Again, GitHub Actions is does the actual publishing (including GitHub release) when there are new tags.
+Again, GitHub Actions is does the actual publishing when there are new tags.
 
 ### Manual release process