chore(deps): update docker.io/library/node docker tag to v26.8.1

.gitea/workflows/markdown-linters.yaml

@@ -13,7 +13,7 @@ on:
 jobs:
   markdown-link-checker:
     container:
-      image: docker.io/library/node:26.8.2-alpine
+      image: docker.io/library/node:26.8.1-alpine
     runs-on: ubuntu-latest
     steps:
     - name: Install tooling
@@ -28,7 +28,7 @@ jobs:
 
   markdown-lint:
     container:
-      image: docker.io/library/node:26.8.2-alpine
+      image: docker.io/library/node:26.8.1-alpine
     runs-on: ubuntu-latest
     steps:
     - name: Install tooling

README.md

@@ -6,14 +6,13 @@ them to `Chart.yaml`.
 
 The action parses conventional commit messages between two Git tags and produces an `artifacthub.io/changes` annotation.
 Pre-release tags according to [SemVer 2.0](https://semver.org/) (e.g. `-alpha`, `-beta.1`, `-rc.2`) are detected
-automatically and additionally result in an `artifacthub.io/prerelease` annotation.
+automatically and result in an `artifacthub.io/prerelease` annotation instead.
 
 ## Usage
 
 ### Auto-detect tags
 
-Without explicit inputs the action uses the currently checked out tag as end tag and the most recent stable
+Without explicit inputs the action determines the two most recent stable (non-pre-release) tags from the Git history:
-(non-pre-release) tag as start tag:
 
 ```yaml
 steps:
@@ -60,11 +59,13 @@ steps:
 ## Pre-releases
 
 Tags containing a hyphen-separated pre-release identifier according to [SemVer 2.0](https://semver.org/) are treated as
-pre-releases (e.g. `v1.0.0-alpha`, `v1.0.0-beta.1`, `v2.0.0-rc.2`). When `new-tag` is a pre-release tag, the action sets
+pre-releases (e.g. `v1.0.0-alpha`, `v1.0.0-beta.1`, `v2.0.0-rc.2`). When `new-tag` is a pre-release tag, the action:
-`artifacthub.io/prerelease: "true"` in `Chart.yaml` in addition to the generated changelog.
 
-When auto-detecting tags (no explicit `old-tag`/`new-tag`), the end tag is the tag of the checked out commit - including
+1. Sets `artifacthub.io/prerelease: "true"` in `Chart.yaml`.
-pre-releases - while the start tag is always the most recent stable tag.
+2. Skips changelog generation entirely.
+
+When auto-detecting tags (no explicit `old-tag`/`new-tag`), the action ignores pre-release tags and selects the two
+most recent stable tags instead.
 
 ## Commit type mapping
 

add-annotations.sh

@@ -23,9 +23,8 @@ if [[ ! -f "${CHART_FILE}" ]]; then
   exit 1
 fi
 
-# Determine old and new tags. The new tag is the currently checked out one - including prereleases - so that
+# Determine old and new tags
-# prereleases are detected. Only the old tag is restricted to stable releases.
+DEFAULT_NEW_TAG="$(git tag --sort=-version:refname | grep --invert-match --perl-regexp "${PRERELEASE_PATTERN}" | head --lines 1)"
-DEFAULT_NEW_TAG="$(git describe --tags --exact-match HEAD 2>/dev/null || git tag --sort=-version:refname | head --lines 1)"
 DEFAULT_OLD_TAG="$(git tag --sort=-version:refname | grep --invert-match --perl-regexp "${PRERELEASE_PATTERN}" | head --lines 2 | tail --lines 1)"
 
 if [[ -n "${INPUT_OLD_TAG:-}" ]]; then
@@ -51,7 +50,9 @@ if [[ -z "$(git tag --list "${NEW_TAG}")" ]]; then
 fi
 
 if [[ "${NEW_TAG}" =~ ${PRERELEASE_PATTERN} ]]; then
+  echo "INFO: Tag '${NEW_TAG}' is a prerelease, setting prerelease annotation and skipping changelog."
   yq --no-colors --inplace ".annotations.\"artifacthub.io/prerelease\" = \"true\" | sort_keys(.)" "${CHART_FILE}"
+  exit 0
 fi
 
 CHANGE_LOG_YAML="$(mktemp)"