chore: migrate to mise

[fallion]

Important

Migrates CI workflow to use mise for tool installation and management, adding .mise.toml for configuration.

• CI Workflow:
  • Replaces Go setup with mise in .github/workflows/test.yml.
  • Adds steps to install and reshim mise before running tests and tidy checks.
• Configuration:
  • Adds .mise.toml to specify Go version 1.25.5.

^{This description was created by for f79f9db. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to af9383c in 58 seconds. Click for details.

• Reviewed 51 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/test.yml:12

• Draft comment:
  Ensure 'mise install' correctly sets up the Go environment per .mise.toml. Verify that the version installed is what's expected.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to verify that the setup is correct and that the version installed is as expected. This falls under the category of asking the author to double-check things, which is against the rules.

2. .github/workflows/test.yml:6

• Draft comment:
  Matrix strategy was removed. Confirm that testing against a single Go version meets your requirements.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. .mise.toml:2

• Draft comment:
  Confirm that using Go version '1.25.5' aligns with your project needs and is compatible with tooling changes.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_KY2locszyYeZHEX4

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 8cbff6f in 54 seconds. Click for details.

• Reviewed 55 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 2 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/test.yml:12

• Draft comment:
  Ensure the removal of setup-go and matrix config is intentional; confirm that 'mise' correctly sets the required Go version for all jobs.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. .mise.toml:1

• Draft comment:
  Verify that Go version 1.25.5 is compatible with your codebase and CI requirements.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_ishfNl7aUxGW11Pf

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed f79f9db in 2 minutes and 50 seconds. Click for details.

• Reviewed 59 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/test.yml:6

• Draft comment:
  Removed matrix and setup-go steps now fix Go to version from .mise.toml (1.25.5). Confirm that testing on a single Go version is intended.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to confirm their intention regarding testing on a single Go version. This violates the rule against asking the author to confirm their intention or ensure behavior is intended. The comment should be removed.

2. .github/workflows/test.yml:21

• Draft comment:
  There are duplicate calls to 'mise reshim' (once as a dedicated step and again in the run blocks). Verify if both are needed to update shims for binaries installed via 'go install'.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% The comment starts with "Verify if both are needed" which is explicitly mentioned in the rules as a type of comment to avoid ("Do NOT ask the PR author to confirm their intention, to explain, to double-check things, to ensure the behavior is intended"). The comment doesn't definitively state that one of the reshim calls is unnecessary - it's speculative and asks for verification. While there may be duplication, the comment doesn't provide clear evidence that this is wrong or actionable guidance on what to change. The first reshim might be needed after mise install, and the second after go install - this could be intentional. Perhaps the duplication is genuinely problematic and wasteful, and the comment is trying to help optimize the workflow. The author might not have realized they're calling reshim twice and this could be a legitimate code quality issue. Even if the duplication might be suboptimal, the comment explicitly asks to "verify if both are needed" rather than stating definitively that one should be removed. This is asking the author to confirm their intention, which violates the rules. If the comment had said "Remove the duplicate reshim call on line X because Y", that would be actionable. This comment should be deleted because it asks the PR author to verify their intention rather than providing clear, actionable guidance. It's speculative about whether both calls are needed, rather than definitively identifying an issue.

3. .mise.toml:1

• Draft comment:
  The new .mise.toml fixes Go to version 1.25.5. Ensure that upgrading from earlier versions (e.g. 1.16.x or 1.24.x) does not break compatibility with your project.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to ensure compatibility with the new Go version, which violates the rule against asking the author to ensure behavior is intended or tested. It does not provide a specific suggestion or point out a specific issue.

Workflow ID: wflow_eu8WkrQcUPSLLMcq

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}