utPLSQL
diff --git a/‎.github/workflows/build.yml
Copy file name to clipboardExpand all lines: .github/workflows/build.yml
+2-2 b/‎.github/workflows/build.yml
Copy file name to clipboardExpand all lines: .github/workflows/build.yml
+2-2
diff --git a/‎.github/workflows/release.yml
Copy file name to clipboardExpand all lines: .github/workflows/release.yml
+1-1 b/‎.github/workflows/release.yml
Copy file name to clipboardExpand all lines: .github/workflows/release.yml
+1-1
diff --git a/‎development/releasing.md
Copy file name to clipboardExpand all lines: development/releasing.md
+1-1 b/‎development/releasing.md
Copy file name to clipboardExpand all lines: development/releasing.md
+1-1
@@ -88,7 +88,7 @@ jobs:
           --health-cmd healthcheck.sh
 
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
       - uses: c-py/action-dotenv-to-setenv@v2
@@ -183,7 +183,7 @@ jobs:
         run:  bash .github/scripts/validate_report_files.sh
 
       - name: Codecov
-        uses: codecov/codecov-action@v2
+        uses: codecov/codecov-action@v4
         with:
           token: ${{ secrets.CODECOV_TOKEN }} # not required for public repos
           files: ./cobertura.xml
 
@@ -16,7 +16,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
       - uses: c-py/action-dotenv-to-setenv@v2
 
@@ -6,7 +6,7 @@ To create a release follow the below steps
    - Create a **draft** of a Release with a new tag number `vX.Y.X`  sourced from the `develop` branch on [github releases page](https://github.com/utPLSQL/utPLSQL/releases) 
    - Populate release description using the `Generate release notes` button
    - Review the auto-generated release notes and update tem if needed
-   - Split the default `## What's Changed` list into `## New features`, `## Enhancements`, `## Bug fixes`. See previous release notes for details
+   - Optionally, split the default `## What's Changed` list into `## New features`, `## Enhancements`, `## Bug fixes`. See previous release notes for details
 
 ## Performing a release
    - Publish [the previously prepared](#release-preparation) release draft.