Merge upstream updates, bump dependencies, and refactor code and unit tests

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @companieshouse/platform-admin

.github/dependabot.yml

@@ -0,0 +1,15 @@
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "monthly"
+    groups:
+      version-updates:
+        applies-to: "version-updates"
+        patterns:
+          - "*"
+      security-updates:
+        applies-to: "security-updates"
+        patterns:
+          - "*"

.github/workflows/unit-tests.yml

@@ -0,0 +1,29 @@
+name: Node.js CI
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  unit-tests:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [25]
+        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
+
+    steps:
+    - name: Check out source code
+      uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+    - name: Set up Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
+      with:
+        node-version: ${{ matrix.node-version }}
+        cache: 'npm'
+    - run: npm ci
+    - run: npm run build --if-present
+    - run: npm test

Dockerfile

@@ -1,9 +1,12 @@
-FROM node:alpine
+FROM node:25-alpine
 WORKDIR /opt/resource
 ADD bin .
+ADD bin/out.js out
 ADD package.json .
 
+RUN npm install -g npm@latest
+
 RUN NODE_ENV=production npm install --quiet
 RUN apk update \
- && apk add jq \
- && rm -rf /var/cache/apk/*
+  && apk add jq \
+  && rm -rf /var/cache/apk/*

README.md

@@ -28,8 +28,8 @@ resources:
     github_token: ((github-token))
 ```
 
--	`github_api`: *Required.* The Github API URL for your repo.
--   `github_token`: *Required.* [A Github token with the `admin:repo_hook` scope.](https://github.com/settings/tokens/new?scopes=admin:repo_hook) Additionally, the token's account must [be an administrator of your repo](https://help.github.com/en/articles/managing-an-individuals-access-to-an-organization-repository) to manage the repo's webhooks.
+- `github_api`: *Required.* The Github API URL for your repo.
+- `github_token`: *Required.* [A Github token with the `admin:repo_hook` scope.](https://github.com/settings/tokens/new?scopes=admin:repo_hook) Additionally, the token's account must [be an administrator of your repo](https://help.github.com/en/articles/managing-an-individuals-access-to-an-organization-repository) to manage the repo's webhooks.
 
 Behavior
 --------
@@ -50,24 +50,61 @@ Create or delete a webhook using the configured parameters.
     webhook_token: your-token
     operation: create
     events: [push, pull_request]
+    pipeline: pipeline-name
+    pipeline_instance_vars: {
+        your_instance_var_name: value
+    }
+    webhook_target_host: your-payload-base-url
+    payload_content_type: json
+    payload_secret: your-payload-secret
 ```
 
--	`org`: *Required.* Your github organization.
--	`repo`: *Required.* Your github repository.
--	`resource_name`: *Required.* Name of the resource to be associated with your webhook.
--	`webhook_token`: *Required.* Arbitrary string to identify your webhook. Must match the `webhook_token` property of the resource your webhook points to.
--	`operation`: *Required.*
-    -   `create` to create a new webhook. Updates existing webhook if your configuration differs from remote.
-    -   `delete` to delete an existing webhook. Outputs current timestamp on non-existing webhooks.
--   `events`: *Optional*. An array of [events](https://developer.github.com/webhooks/#events) which will trigger your webhook. Default: `push`
+- `org`: *Required.* Your github organization.
+- `repo`: *Required.* Your github repository.
+- `resource_name`: *Required.* Name of the resource to be associated with your webhook.
+- `webhook_token`: *Required.* Arbitrary string to identify your webhook. Must match the `webhook_token` property of the resource your webhook points to.
+- `operation`: *Required.*
+  - `create` to create a new webhook. Updates existing webhook if your configuration differs from remote.
+  - `delete` to delete an existing webhook. Outputs current timestamp on non-existing webhooks.
+- `events`: *Optional*. An array of [events](https://developer.github.com/webhooks/#events) which will trigger your webhook. Default: `push`
+- `pipeline`: *Optional.* Defaults to the name of the pipeline executing the task
+- `pipeline_instance_vars`: *Optional.* Instance vars to append to the webhook url. These help Concourse identify which [instance pipeline](https://concourse-ci.org/resources.html#schema.resource.webhook_token) it should invoke
+- `webhook_target_host`: *Optional.* The base URL to send the webhook payload to. Defaults to the external Concourse URL of the pipeline executing the task.
+- `payload_content_type`: *Optional.* Default: `form`
+  - `json` to serialize payloads to JSON.
+  - `form` to serialize payloads to x-www-form-urlencoded.
+- `payload_secret`: *Optional.* Secret that is used as the key to generate [delivery signature headers](https://docs.github.com/en/webhooks/webhook-events-and-payloads#delivery-headers), if the destination requires it for delivery validation.
+
+## Example
+Include the github-webhook-resource in your pipeline.yml file
+
+```yaml
+resource_types:
+  - name: github-webhook-resource
+    type: docker-image
+    source:
+      repository: homedepottech/github-webhook-resource
+      tag: latest 
+```
+
+Now when you set your pipeline, you can optionally include instance variables that will be picked up by the resource. Here is a sample script that sets the pipeline for you. 
+
+```bash
+#!/bin/sh
+
+fly -t {your team name} sp -c pipeline.yml -p {your pipeline name} --instance-var {you instance variables}
+
+
+```
 
 ## Development
+
 ### Prerequisites
 - [Node.js](https://nodejs.org/)
 - [Docker](https://www.docker.com/)
 
 ### Making changes
-The Concourse entrypoints are in `bin/check`, `bin/in`, and `bin/out`. You can add functionality to these files directly, or you can `require` additional supporing files.
+The Concourse entrypoints are in `bin/check`, `bin/in`, and `bin/out.js`. You can add functionality to these files directly, or you can `require` additional supporing files.
 
 See the [Reference](#Reference) section for some helpful information related to this project's implementation.
 

SUPPORT.md

@@ -5,4 +5,4 @@ If you encounter a bug with the *github-webhook-resource*, please [file an issue
 If you would like to contribute to the project, please read the [CONTRIBUTING](CONTRIBUTING.md) file.
 
 # Contact us
-Reach out to one of our [MAINTAINERS.](MAINTAINERS.md)
+Reach out to one of our [MAINTAINERS.](MAINTAINERS.md)