feat: add version-file input

[acouvreur]

You can now use .tool-versions file to specify GoReleaser version to download

Closes #541

---

Testing

With version-file referencing a non-existing file

Typo .tools-version instead of .tool-versions

sablierapp/sablier@0700179

With version-file referencing .tool-versions file

sablierapp/sablier@94739c4

No version specified

sablierapp/sablier@d5d4432

[caarlos0]

looks good - could you add tests as well? there's a bunch in there, you can follow their lead

[acouvreur]

@caarlos0 just added a test file!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.78%. Comparing base (14707cd) to head (9307d0b).
⚠️ Report is 66 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #542      +/-   ##
==========================================
+ Coverage   66.92%   68.78%   +1.86%     
==========================================
  Files           3        4       +1     
  Lines         130      157      +27     
  Branches       23       43      +20     
==========================================
+ Hits           87      108      +21     
- Misses         27       49      +22     
+ Partials       16        0      -16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[acouvreur]

Hey sorry about the missing unused imports, I will clean it up

[acouvreur]

@caarlos0 I've updated the test file to remove the unused imports, tell me if that
s good for you!

[caarlos0]

i wonder if it would be better to simplify all this making version-file having precedence

so, if version-file is given, use it, or error

otherwise, use version, which would also mean we don't need to manually default to ~> v2

wdyt?

[acouvreur]

I think it is a better solution indeed because then I can revert all the changes about how the default version is computed.

I've taken much inspiration from the current implementation in the goreleaser action, so I've essentially implemented the same behavior.

Let me change it with your suggestion.

[Copilot]

Pull request overview

Adds support for selecting the GoReleaser version via a version-file input (currently .tool-versions), with parsing logic and tests.

Changes:

• Introduced getRequestedVersion() to resolve version from version or version-file.
• Wired resolved version into the installation flow in src/main.ts.
• Documented the new input and added Jest coverage for version resolution.

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
src/version.ts	Adds logic to resolve GoReleaser version from .tool-versions (or fall back to version).
src/main.ts	Uses resolved version when installing GoReleaser.
src/context.ts	Adds versionFile input wiring.
action.yml	Declares new version-file input.
tests/version.test.ts	Adds Jest tests for version resolution behavior.
README.md	Documents version-file and updates TOC / inputs list.

---

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

[Copilot]

This always resolves version-file relative to workdir when workdir is set (including common monorepo setups where workdir is a subdirectory). That makes it impossible to reference a version file in the repo root while also using a non-root workdir, despite the docs saying the path can be relative to the root or workdir. Consider resolving relative paths by checking both candidates (repo root path first, then path.join(workdir, versionFile)), or updating the docs to state that version-file is interpreted relative to workdir when provided.

[Copilot]

If .tool-versions doesn’t contain a goreleaser ... entry, this sets requestedVersion to an empty string, which will likely cause a confusing failure later during install. Prefer throwing a clear error when no matching entry is found (e.g., file exists but no goreleaser line), so users get an actionable message.

Suggested change

	requestedVersion = match ? 'v' + match[1].trim().replace(/^v/gi, '') : '';
	if (!match) {
	throw new Error(
	`No 'goreleaser' entry found in ${versionFilePath}. ` +
	"Please add a line like 'goreleaser <version>' or specify the version input directly."
	);
	}
	requestedVersion = 'v' + match[1].trim().replace(/^v/gi, '');

[Copilot]

The parser requires goreleaser to start at column 0. .tool-versions files sometimes contain leading whitespace; allowing optional leading spaces (e.g., ^\\s*goreleaser\\s+... with the m flag) would make the parsing more robust without changing intended behavior.

Suggested change

	const match = content.match(/^goreleaser\s+([^\n#]+)/m);
	const match = content.match(/^\s*goreleaser\s+([^\n#]+)/m);

[Copilot]

There isn’t a test covering the case where .tool-versions exists but has no goreleaser entry (or has a malformed one). If getRequestedVersion() is updated to throw a specific error for that scenario (recommended), please add a Jest test asserting that behavior (ideally also asserting the error message).

[Copilot]

There isn’t a test covering the case where .tool-versions exists but has no goreleaser entry (or has a malformed one). If getRequestedVersion() is updated to throw a specific error for that scenario (recommended), please add a Jest test asserting that behavior (ideally also asserting the error message).

[Copilot]

There isn’t a test covering the case where .tool-versions exists but has no goreleaser entry (or has a malformed one). If getRequestedVersion() is updated to throw a specific error for that scenario (recommended), please add a Jest test asserting that behavior (ideally also asserting the error message).

Suggested change

	it('throws when .tool-versions exists but has no goreleaser entry', () => {
	const toolVersionsPath = path.join(tmpDir, '.tool-versions');
	fs.writeFileSync(toolVersionsPath, 'nodejs 20.0.0\n');
	const inputs: Inputs = {
	distribution: 'goreleaser',
	version: '',
	versionFile: '.tool-versions',
	args: '',
	workdir: tmpDir,
	installOnly: false
	};
	expect(() => getRequestedVersion(inputs)).toThrow(/goreleaser/i);
	});
	it('throws when .tool-versions has a malformed goreleaser entry', () => {
	const toolVersionsPath = path.join(tmpDir, '.tool-versions');
	fs.writeFileSync(toolVersionsPath, 'goreleaser not-a-version\n');
	const inputs: Inputs = {
	distribution: 'goreleaser',
	version: '',
	versionFile: '.tool-versions',
	args: '',
	workdir: tmpDir,
	installOnly: false
	};
	expect(() => getRequestedVersion(inputs)).toThrow(/goreleaser/i);
	});

[Copilot]

There isn’t a test covering the case where .tool-versions exists but has no goreleaser entry (or has a malformed one). If getRequestedVersion() is updated to throw a specific error for that scenario (recommended), please add a Jest test asserting that behavior (ideally also asserting the error message).

[caarlos0]

Hi @acouvreur — thanks a lot for this contribution! I'm taking the work over in #556 to add more test coverage and tighten parsing edge cases (inline comments, asdf fallback lists, error messages). The original feature design is preserved. Crediting you as co-author on the commit.

[caarlos0]

merged in #556 - thanks!