Skip to content

docs: update version examples and CI/CD tooling references #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Amnoor merged 1 commit into from
Apr 4, 2026
+12 −2
Merged

docs: update version examples and CI/CD tooling references #92

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,12 +175,12 @@ Applications that need a different timezone can set `TZ` at runtime (timezone da
## Versioning and Tags

Tags follow the pattern:
- `v<major>.<minor>.<patch>+node<node_version>` (example: `v1.2.4+node24.14.1`)
- `v<major>.<minor>.<patch>+node<node_version>` (example: `v1.2.6+node24.14.1`)
- `latest` tracks the most recent release.

Check the GitHub Releases page for the current tag and Node.js version.

> Because of the `docker/metadata-action`, all tags with `+`, turns into `-` (example: GitHub Releases `v1.2.4+node24.14.1` then it becomes `v1.2.4-node24.14.1` in the Docker Hub and GitHub Container Registry)
> Because of the `docker/metadata-action`, all tags with `+`, turns into `-` (example: GitHub Releases `v1.2.6+node24.14.1` then it becomes `v1.2.6-node24.14.1` in the Docker Hub and GitHub Container Registry)

## Security Posture

Expand Down Expand Up @@ -245,6 +245,16 @@ Runtime Node exists because of a small set of outstanding open-source projects t

[**actions/checkout**](https://github.com/actions/checkout) — GitHub Action used to check out the repository code in every workflow job.

[**actions/upload-artifact**](https://github.com/actions/upload-artifact) — GitHub Action used to persist validation artifacts between workflow jobs.

[**actions/download-artifact**](https://github.com/actions/download-artifact) — GitHub Action used to retrieve previously uploaded validation artifacts for later test steps.

[**geekyeggo/delete-artifact**](https://github.com/geekyeggo/delete-artifact) — GitHub Action used to remove temporary workflow artifacts after validation completes.

[**chrnorm/deployment-action**](https://github.com/chrnorm/deployment-action) — GitHub Action used to create GitHub Deployment records during release and promotion workflows.

[**chrnorm/deployment-status**](https://github.com/chrnorm/deployment-status) — GitHub Action used to publish deployment state updates back to GitHub during release and promotion workflows.

### Contributors

| | Name | GitHub | Role |
Expand Down
Loading