Updated workflows and README

Author: LimeEng

.github/workflows/node.yml .github/workflows/ci.yaml.github/workflows/node.yml renamed to .github/workflows/ci.yaml

@@ -1,20 +1,18 @@
-name: Node CI
+name: CI
 
 on: [push, pull_request]
 
 jobs:
   build:
-
     runs-on: ubuntu-latest
-
     strategy:
       matrix:
-        node-version: [14.x, 16.x]
+        node-version: [lts/-1, lts/*]
 
     steps:
-    - uses: actions/checkout@v1
+    - uses: actions/checkout@v4
     - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
+      uses: actions/setup-node@v4
       with:
         node-version: ${{ matrix.node-version }}
     - name: npm install

.github/workflows/release.yml .github/workflows/release.yaml.github/workflows/release.yml renamed to .github/workflows/release.yaml

@@ -8,21 +8,21 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v1
-      - uses: actions/setup-node@v1
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
         with:
-          node-version: 14
+          node-version: lts/*
       - run: npm install --ignore-scripts
       - run: npm test
 
   publish-npm:
     needs: build
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v1
-      - uses: actions/setup-node@v1
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
         with:
-          node-version: 14
+          node-version: lts/*
           registry-url: https://registry.npmjs.org/
       - run: npm install --ignore-scripts
       - run: npm publish --access public

README.md

@@ -1,10 +1,9 @@
-![](https://github.com/LimeEng/NodeSemaphore/workflows/Node%20CI/badge.svg)
+![](https://github.com/LimeEng/NodeSemaphore/actions/workflows/ci.yaml/badge.svg)
 [![npm (scoped)](https://img.shields.io/npm/v/@limeeng/semaphore.svg)](https://www.npmjs.com/package/@limeeng/semaphore)
 
 # Node Semaphore
 
-What is a semaphore? A great explanation is available at [Wikipedia](https://en.wikipedia.org/wiki/Semaphore_(programming)).
-It is basically a simple way to control access to resources in concurrent systems. One might think that there is no need for semaphores in JavaScript since it is single-threaded by nature, but in some cases it is absolutely necessary. Race conditions can still manifest and there are several legitimate reasons for wanting to throttle concurrency when working with asynchronous systems.
+[Semaphores](https://en.wikipedia.org/wiki/Semaphore_(programming) can be used to control access to resources in concurrent systems. While JavaScript is inherently single-threaded, semaphores can still help manage asynchronous operations and prevent issues like resource contention.
 
 - [Installation](#install)
 - [API](#api)