BUILD-11553 Use RUNNER_TEMP for get-build-number cache file

[matemoln]

Write build_number.txt under RUNNER_TEMP instead of the workspace checkout so ephemeral cache state does not pollute the repository tree.

[hashicorp-vault-sonar-prod]

BUILD-11553

[Copilot]

Pull request overview

This PR updates the get-build-number composite action and its ShellSpec tests to store the cached build_number.txt under RUNNER_TEMP (instead of the workspace checkout), preventing ephemeral cache state from modifying the repository tree during workflow runs.

Changes:

• Update the action to write/read the build number file via a BUILD_NUMBER_FILE path pointing to ${RUNNER_TEMP}/build_number.txt.
• Update the underlying get_build_number.sh script to use BUILD_NUMBER_FILE / RUNNER_TEMP for its cache file location.
• Adjust ShellSpec tests to set RUNNER_TEMP and assert the cache file is created in the temp directory.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
spec/get_build_number_spec.sh	Sets RUNNER_TEMP in tests and updates assertions to expect the cache file in temp.
get-build-number/get_build_number.sh	Uses BUILD_NUMBER_FILE / RUNNER_TEMP to determine where to write the cache file.
get-build-number/action.yml	Exports BUILD_NUMBER_FILE into the composite action environment and updates cache/read/write steps to use it.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gitar-bot]

Code Review ✅ Approved

Updates the build number cache location to use RUNNER_TEMP instead of the workspace directory. This change prevents ephemeral build artifacts from polluting the repository tree.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud