Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/ISSUE_TEMPLATE/feature_request.yml:
- Around line 21-22: The link target "../.github/workflows/release.yml" in the
note line "📝 **Note:** The version list is automatically updated when a new
release is created. See
[`.github/workflows/release.yml`](../.github/workflows/release.yml) for
details." is incorrect; update the markdown link target to the correct relative
path "./workflows/release.yml" (or simply ".github/workflows/release.yml" as
appropriate) in the same note in both the feature_request.yml and bug report.yml
templates so the `[`.github/workflows/release.yml`]` link points to the actual
release workflow file.

In @.github/workflows/release.yml:
- Around line 112-130: The "Update version in issue templates" step is
inserting/removing the wrong lowercase token and uses stale hard-coded versions;
update the sed operations to use the exact "OpenSourcePOS ${NEW_VERSION}" casing
(reference BUG_TEMPLATE and FEATURE_TEMPLATE and the sed insertions) and make
the cleanup/remove targets dynamic instead of fixed numbers—use patterns that
remove duplicates/older entries by matching "OpenSourcePOS" regardless of
previous numeric value (or derive the previous versions from NEW_VERSION) so the
insertions and deletions operate on the same exact token and no stale hard-coded
versions remain.
- Around line 211-218: The workflow captures SHORT_SHA too early causing the
release archive to be unreproducible; update the build_version step (and the
equivalent steps at 225-228 and 254-257) to compute SHORT_SHA only after the
release commit/tag that includes the final packaged files exists (i.e., after
any git add/git commit for modified files and after creating the release tag),
or derive the short SHA from the final tag/commit (git rev-parse --short=6
<tag-or-final-commit>) so the recorded short-sha and version-tag match the exact
commit used to build the archive.
- Around line 151-155: The script adds NEW_LINK but doesn't update the
[unreleased] comparison, leaving it pointed at PREVIOUS_VERSION; after creating
NEW_LINK you should update the [unreleased] link (CHANGELOG_FILE) to compare
from ${NEW_VERSION} to HEAD (e.g. set the [unreleased] link to
"https://github.com/opensourcepos/opensourcepos/compare/${NEW_VERSION}...HEAD");
implement this by adding a sed (or similar) step that locates the line starting
with "[unreleased]:" or the existing [unreleased] link and replaces its URL to
use ${NEW_VERSION}...HEAD so Unreleased no longer includes already released
commits.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/ISSUE_TEMPLATE/feature_request.yml:
- Around line 39-50: The dropdown for id "ospos-version" in the feature_request
template is missing "OpenSourcePOS 3.3.8" and now diverges from the bug report
template; update the options array for the ospos-version dropdown to include
"OpenSourcePOS 3.3.8" (matching the bug report.yml) and verify both templates'
option lists are kept in sync (or centralize the version list) so future edits
don't diverge.

In @.github/workflows/release.yml:
- Around line 121-126: The sed invocation expands $COMMITS directly which can
contain sed metacharacters and break the command; instead write the safe content
(VERSION_HEADER, a blank line, and $COMMITS) to a temp file using a quoted
redirection (e.g. via mktemp and printf '%s\n' "$VERSION_HEADER" "" "$COMMITS" >
"$TMP"), then use sed's file-insert action to read that file into CHANGELOG_FILE
(e.g. sed -i '/^## \[Unreleased\]/r '"$TMP" ' "$CHANGELOG_FILE"') so sed never
interprets commit text as script, and finally rm the temp file to clean up.

---

Nitpick comments:
In @.github/workflows/release.yml:
- Around line 31-36: Validate the extracted CURRENT_VERSION after the grep/sed
step in the "Get current version" job (id: current_version) to ensure it's
non-empty and matches the expected version pattern; if validation fails, emit a
clear error with process output and exit non-zero so downstream steps do not
run. Specifically, after assigning CURRENT_VERSION (from the grep/sed pipeline)
check for emptiness and optionally match a semantic version regex (e.g., digits
and dots), log "Invalid or empty CURRENT_VERSION: $CURRENT_VERSION" to the
workflow output, and fail the step immediately to prevent silent
arithmetic/file-update errors.
- Around line 139-141: The release job currently runs git add followed by git
commit -m "chore: release version $NEW_VERSION" and git push origin HEAD, which
will fail when there are no staged changes; update the workflow to detect
whether there are staged changes before committing (e.g., run a check like git
diff --cached --quiet or inspect git status --porcelain) and only run git commit
and git push when changes exist, otherwise skip/echo a clear message; ensure the
check is placed around the existing git add / git commit / git push sequence so
the steps referencing those symbols (git add, git commit -m "chore: release
version $NEW_VERSION", git push origin HEAD) are conditionally executed.

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.github/ISSUE_TEMPLATE/feature_request.yml:
- Around line 45-50: The release workflow currently hardcodes removal of
"OpenSourcePOS 3.3.7" which prevents proper rotation; update the step in the
release workflow that trims the changelog/version list so it computes and
removes the oldest entry dynamically (e.g., split the list by lines, keep only
the N newest entries or remove the last line) instead of matching a specific
version string; modify the script/command used in the workflow job (the step
that runs the sed/awk/bash trimming command) to use a robust regex or array
slicing approach that always retains the top N versions and drops the rest so
future version bumps don’t append without trimming.