Use make backend in VS Code tasks.json

[silverwind]

The previous bare go build did not pass -ldflags, so main.Version was never set and defaulted to "development". This caused AssetVersion to always be "development", meaning browser cache was never busted between frontend rebuilds during development.

AssetVersion before: 1.26.0+dev
AssetVersion after: 1.26.0+dev-548-g6e8f78ae27

[Copilot]

Pull request overview

Updates the VS Code build tasks to invoke the repo’s make backend target so development builds get the same -ldflags-derived version metadata as standard builds, which fixes asset cache busting during frontend rebuilds.

Changes:

• Replace the VS Code “Build” task from go build to make backend.
• Replace the VS Code “Build (with SQLite3)” task from go build -tags ... to make backend with TAGS=....

---

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

You can also share your feedback on Copilot code review. Take the survey.

[lafriks]

there won't be make on windows, whole point for this is to work without make for local development, otherwise you can just use make already from cli imho

[silverwind]

make is available for Windows and already a required development dependency. Not using make would be a suboptimal development experience.

I guess I can hack around and make it work without make but the point stands that it's not optimal to circumvent make.

[silverwind]

I will check what's needed to eliminate make here, even thought I think the make-less startup process is inherently flawed.

[silverwind]

This will be fixed with #36896 where there will not be any more AssetVersion problems.