diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index a93e0fe..e16f5b6 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -9,15 +9,15 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Set Up Git Repository
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
       - name: Compile LaTeX Document
-        uses: xu-cheng/latex-action@v2
+        uses: xu-cheng/latex-action@v3
         with:
           work_in_root_file_dir: true
           root_file: |
             src/main.tex
       - name: Release
-        uses: softprops/action-gh-release@v1
+        uses: softprops/action-gh-release@v2
         with:
           generate_release_notes: true
           files: |
diff --git a/README.md b/README.md
index 7d4bc66..4f1c34e 100644
--- a/README.md
+++ b/README.md
@@ -17,9 +17,9 @@ Make changes to the LaTeX documents, and provide [git-tags](https://git-scm.com/
 
 Automation of LaTeX project build and tag-based releases is achieved with [GitHub Actions](https://github.com/features/actions). The workflow configuration is achieved with [`release.yml`](./.github/workflows/release.yml) file. The workflow dependencies are listed as follows:
 
-- [actions/checkout@v2](https://github.com/actions/checkout)
-- [xu-cheng/latex-action@v2](https://github.com/xu-cheng/latex-action)
-- [softprops/action-gh-release@v1](https://github.com/softprops/action-gh-release)
+- [actions/checkout](https://github.com/actions/checkout)
+- [xu-cheng/latex-action](https://github.com/xu-cheng/latex-action)
+- [softprops/action-gh-release](https://github.com/softprops/action-gh-release)
 
 ## LaTeX Document Hierarchy
 
@@ -35,6 +35,6 @@ The sample LaTeX document hierarchy is in the form below. It is a minimal demons
     └── my_table.tex
 ```
 
-As expected, building process depends on the document hierarchy. This template is designed for the base case provided in [xu-cheng/latex-action@v2](https://github.com/xu-cheng/latex-action) such that we have a single `root_file: main.tex`, and we are compiling with default settings of [xu-cheng/latex-action@v2](https://github.com/xu-cheng/latex-action). The provided hierarchy can be changed easily, however [`release.yml`](./.github/workflows/release.yml) needs to be changed, accordingly. Since [xu-cheng/latex-action@v2](https://github.com/xu-cheng/latex-action) provides a rich documentation, this aspect should not be problematic.
+As expected, building process depends on the document hierarchy. This template is designed for the base case provided in [xu-cheng/latex-action](https://github.com/xu-cheng/latex-action) such that we have a single `root_file: main.tex`, and we are compiling with default settings of [xu-cheng/latex-action](https://github.com/xu-cheng/latex-action). The provided hierarchy can be changed easily, however [`release.yml`](./.github/workflows/release.yml) needs to be changed, accordingly. Since [xu-cheng/latex-action](https://github.com/xu-cheng/latex-action) provides a rich documentation, this aspect should not be problematic.
 
-Finally, the [softprops/action-gh-release@v1](https://github.com/softprops/action-gh-release) action creates a release based on the provided tag, and adds the generated `main.pdf` from workspace directory to the assets of release. If a hierarchy change is on the table, then the release aspect of [`release.yml`](./.github/workflows/release.yml) needs to be altered, accordingly.
+Finally, the [softprops/action-gh-release](https://github.com/softprops/action-gh-release) action creates a release based on the provided tag, and adds the generated `main.pdf` from workspace directory to the assets of release. If a hierarchy change is on the table, then the release aspect of [`release.yml`](./.github/workflows/release.yml) needs to be altered, accordingly.