Release 1.2.0

.github/CONTRIBUTING.md

@@ -0,0 +1,92 @@
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via issue,
+email, or any other method with the owners of this repository before making a change. 
+
+Please note we have a code of conduct, please follow it in all your interactions with the project.
+
+## Pull Request Process
+
+1. Ensure any install or build dependencies are removed before the end of the layer when doing a 
+   build.
+2. Update the README.md with details of changes to the interface, this includes new environment 
+   variables, exposed ports, useful file locations and container parameters.
+3. Increase the version numbers in any examples files and the README.md to the new version that this
+   Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
+4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you 
+   do not have permission to do that, you may request the second reviewer to merge it for you.
+
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at info@venly.io. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2018-present, Venly.io
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

.github/actions/bump_version/action.yml

@@ -0,0 +1,51 @@
+name: 🔖 Bump Build Version
+description: "Bump Build Version"
+
+inputs:
+  token:
+    description: GitHub token for authentication
+    required: true
+
+outputs:
+  new_version:
+    description: "Bumped Version"
+    value: ${{ steps.bump_version.outputs.new_version }}
+
+runs:
+  using: "composite"
+  steps:
+    - uses: oleksiyrudenko/gha-git-credentials@v2.1.1
+      with:
+        global: false
+        name: ${{ github.actor }}
+        email: ${{ github.actor }}@venly.io
+        actor: ${{ github.actor }}
+        token: ${{ inputs.token }}
+
+    - name: 🔖 Bump Version
+      id: bump_version
+      shell: bash
+      run: |
+        #!/bin/bash
+        set -x
+        new_version=$(npm version prerelease --preid=develop --git-tag-version=false)
+        new_version=${new_version#v}
+        echo "Version after bump: $(jq -r '.version' package.json)"
+        echo "new_version=$new_version" >> $GITHUB_ENV
+        echo "new_version=$new_version" >> $GITHUB_OUTPUT
+
+    - name: Commit version bump
+      id: commit_version_bump
+      shell: bash
+      run: |
+        #!/bin/bash
+        set -x
+        git commit -a -m ${{ steps.bump_version.outputs.new_version }}
+
+    - name: Push version bump
+      id: push_version_bump
+      shell: bash
+      run: |
+        #!/bin/bash
+        set -x
+        git push origin

.github/actions/cleanup_npm_versions/action.yml

@@ -0,0 +1,45 @@
+name: 🧹 Cleanup Old Develop Versions
+description: "Remove old develop pre-release versions from npm where the base version is <= the just-released version"
+
+runs:
+  using: "composite"
+  steps:
+    - name: 🧹 Cleanup old develop versions
+      shell: bash
+      run: |
+        #!/bin/bash
+        set -x
+
+        package_name=$(jq -r '.name' package.json)
+        released_version="$published_version"
+
+        if [[ -z "$released_version" ]]; then
+          echo "No published_version found, skipping cleanup"
+          exit 0
+        fi
+
+        echo "Released version: $released_version"
+
+        # Set registry for @venly scope
+        npm config set @venly:registry https://registry.npmjs.org/
+
+        # Get all versions from npm
+        all_versions=$(npm view "$package_name" versions --json 2>/dev/null | jq -r '.[]')
+
+        unpublished_count=0
+
+        for version in $all_versions; do
+          # Only target develop pre-release versions
+          if [[ "$version" =~ ^([0-9]+\.[0-9]+\.[0-9]+)-develop\.[0-9]+$ ]]; then
+            version_base="${BASH_REMATCH[1]}"
+
+            # Check if version_base <= released_version (sort -V puts the higher version last)
+            higher=$(printf '%s\n%s' "$version_base" "$released_version" | sort -V | tail -1)
+            if [[ "$higher" == "$released_version" ]]; then
+              echo "Unpublishing ${package_name}@${version}"
+              npm unpublish "${package_name}@${version}" && ((unpublished_count++)) || echo "Failed to unpublish ${version}, continuing..."
+            fi
+          fi
+        done
+
+        echo "Cleanup complete. Unpublished ${unpublished_count} old develop version(s)."

.github/actions/get_version/action.yml

@@ -0,0 +1,32 @@
+name: version
+description: "Reads the version number from package.json"
+
+outputs:
+  version:
+    description: "Version from package.json"
+    value: ${{ steps.package-version.outputs.current_version }}
+
+runs:
+  using: "composite"
+  steps:
+    - name: ❔ get-npm-version ❔
+      id: package-version
+      shell: bash
+      run: |
+        #!/bin/bash
+        set -x
+        PACKAGE_JSON_PATH="./package.json"
+        if [[ -f "$PACKAGE_JSON_PATH" ]]; then
+            VERSION=$(jq -r '.version' "$PACKAGE_JSON_PATH")
+            if [[ "$VERSION" == "null" || -z "$VERSION" ]]; then
+              echo "No version field found in $PACKAGE_JSON_PATH"
+              echo "current_version=0.0.0" >> $GITHUB_ENV
+            else
+              echo "Version in $PACKAGE_JSON_PATH is $VERSION"
+              echo "current_version=$VERSION" >> $GITHUB_ENV
+              echo "current_version=$VERSION" >> $GITHUB_OUTPUT
+            fi
+        else
+            echo "$PACKAGE_JSON_PATH not found"
+            echo "current_version=0.0.0" >> $GITHUB_ENV
+        fi

.github/actions/hotfix_finish/README.md

@@ -0,0 +1,47 @@
+# Hotfix Node Application Finish
+
+This GitHub Action concludes the hotfix process for a Node.js application. It finalizes the hotfix version, merges the hotfix into the production branch, tags the release, publishes the hotfix, and cleans up the hotfix branch.
+
+## Inputs
+
+| Input  | Description                      | Required |
+|--------|----------------------------------|----------|
+| `token`| The VENLY_GITHUB_ACTIONS_TOKEN.  | Yes      |
+
+## Runs
+
+This action operates using the "composite" run type and carries out the steps outlined below:
+
+1. **Set HOME environment variable** to define a consistent workspace for the action.
+2. **Setup Git Credentials** to ensure access to the repository for operations such as checkout, commit, and push.
+3. **Determine Master or Main** to identify the production branch.
+4. **Checkout production branch** to apply the hotfix.
+5. **Setup Node.js environment** with the specified Node.js version (defaults to 16.x).
+6. **Identify the hotfix branch** by fetching remote branches and filtering for the hotfix pattern.
+7. **Switch to the hotfix branch** to finalize the version and prepare for merging.
+8. **Bump Version and Create Tag** using npm to finalize the hotfix version and prepare for release.
+9. **Get npm version for hotfix** to capture the new version number from `package.json`.
+10. **Checkout and Merge to Production Branch** to apply the hotfix changes to the production codebase.
+11. **Publish Hotfix** using GitHub Releases to distribute the hotfix version.
+12. **Switch to Development Branch** to integrate the hotfix changes into the ongoing development work.
+13. **Merge to Develop** to synchronize the development branch with the hotfix and production changes.
+14. **Push Changes** to both develop and production branches to finalize the hotfix process.
+15. **Cleanup Release Branch** by deleting the hotfix branch to clean up the repository.
+
+## Hotfix Flow Info
+
+This action also provides detailed information about the hotfix process, including the workflow name, actor, repository, reference, hotfix version, commit SHA, run ID, and run number.
+
+## Example Usage
+
+```yaml
+jobs:
+  hotfix_finish_job:
+    runs-on: docker-runner
+    name: Finish Hotfix Node Application
+    steps:
+      - name: Hotfix Node App Finish
+        uses: Venly/venly-github-workflows/.github/actions/hotfix_java_start@main
+        with:
+          token: ${{ secrets.VENLY_GITHUB_ACTIONS_TOKEN }}
+```