[cli] Bump x/tools to 0.17.0 to fix compatiblity with go 1.22

[stffabi]

Fixes #3242

Summary by CodeRabbit

• Bug Fixes
  • Fixed compatibility issues with the Wails CLI for Go version 1.22 and later.

[coderabbitai]

Walkthrough

The overall change addresses a specific compatibility issue where the Wails CLI would encounter a panic when built with Go 1.22 and later versions, particularly on Windows. The fix ensures that projects using Wails can now be built successfully without runtime errors, enhancing the stability and reliability of the build process.

Changes

File Path	Change Summary
website/src/pages/.../changelog.mdx	Fixed compatibility for the Wails CLI with Go 1.22+.

Assessment against linked issues

Objective	Addressed	Explanation
Resolve panic when building with Go 1.22 and Wails v2.7.1 on Windows (#3242)	✅
Identify and resolve the bug causing the panic in the Wails library, ensuring application stability (#3224)	❓	The change mentions compatibility with Go 1.22 but does not detail if the specific panic in libraries like go-webview2 and wails is directly addressed.
Address the compilation failure with wails build -compiler due to Go version discrepancies (#3120)	❌	The provided summary does not indicate changes related to the -compiler flag or Go version discrepancies in the build process.

Related issues

• Issue invalid memory address or nil pointer dereference #3224: This issue might be related as it involves a panic error similar to the one addressed in the PR, suggesting a potential fix for the underlying problem in the Wails library.

Poem

In the world of code, where bugs often hop,
A rabbit worked hard, with a skip and a pop.
🐾🛠️ With Go 1.22, it fixed a great plight,
"No more panics," it said, "on this bright night!"

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 72e12ef and 1ca7eda.

Files ignored due to path filters (2)

• v2/go.mod is excluded by: !**/*.mod
• v2/go.sum is excluded by: !**/*.sum

Files selected for processing (1)

• website/src/pages/changelog.mdx (1 hunks)

[coderabbitai]

The changelog entry for the compatibility fix with Go 1.22 should include the PR number for traceability.

- Fixed compatibility for wails cli being built with go 1.22 and later. Fixed by @stffabi
+ Fixed compatibility for wails cli being built with go 1.22 and later. Fixed by @stffabi in [PR](https://github.com/wailsapp/wails/pull/3244)

---

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

- Fixed compatibility for wails cli being built with go 1.22 and later. Fixed by @stffabi in [PR](https://github.com/wailsapp/wails/pull/3244)

[stffabi]

The PR is linked in the changelog and this is in line with all other changelog entries and the guidelines of the Wails project.

[coderabbitai]

@stffabi: Acknowledged. Thank you for the clarification.

[cloudflare-pages]

Deploying with    Cloudflare Pages

Latest commit:	1ca7eda
Status:	✅  Deploy successful!
Preview URL:	https://629b17bb.wails.pages.dev
Branch Preview URL:	https://bugfix-go-1-22-compat.wails.pages.dev

View logs

[leaanthony]

Amazing find! 🙏