Spin 2.6 release

[mikkelhegn]

This is a test, to start creating issues to track Spin releases.

Last week it was decided to release Spin 2.6 this week: https://docs.google.com/document/d/1EG392gb8Eg-1ZEPDy18pgFZvMMrdAEybpCSufFXoe00/edit#bookmark=id.mqvnq7lc0rxb

This issue will track the release.

Release process: https://github.com/fermyon/spin/blob/main/docs/content/release-process.md

• Release engineer assigned
• Release manager assigned

Blockers/Issues to track

• Add deprecation warning for uncomponentizable modules #2571
  • Backport: [Backport v2.6] Add deprecation warning for uncomponentizable modules #2578
• Spin apps are no longer allowed to set host headers with Wasmtime 21.0.1 #2575
• chore(release): bumps for 2.6 release #2573

[mikkelhegn]

Remember: https://docs.google.com/document/d/1EG392gb8Eg-1ZEPDy18pgFZvMMrdAEybpCSufFXoe00/edit#bookmark=id.bswmcj3sc1eu @lann to help write the deprecation warning. #2552

[mikkelhegn]

Assigning myself as release manager and issue owner.

Still looking for an release engineer.

[vdice]

I can be the release engineer

[mikkelhegn]

#2575 is currently blocking this release.

#2575 has been closed, and we are unblocked.

[mikkelhegn]

@itowlson - do we have docs queued up for this feature? #2524. Based on the PR, I'm not sur eI know how to use it :-)

[itowlson]

https://github.com/fermyon/developer/pull/1306/files#diff-508d3554fb5ddeccc9029f9f1d60e906e57f4179ca3ec5dfea6e3d77c06ac249R180

[itowlson]

I am wondering if we should pull the docs though. The publish workflow is distinctly early-stage, and people trying to use registry packages by "what seems obvious" are likely to get themselves burned. It will be more useful once there are pre-published components in registries that people can Just Use.

[mikkelhegn]

In combination with this feature: #2479 - which I got working 🙌🏻 it would be nice to showcase, at least in a release blog, how we're making Spin simply work with Wasm components. Thoughts?

A follow-up on #2479, will this work with any component exporting any handler supported by the Spin installation (including plugins)?

[itowlson]

#2479 is HTTP only.

[lann]

will this work with any component exporting any handler supported by the Spin installation (including plugins)?

We don't currently have a way to determine which trigger type to use. We've discussed in the past adding a spin up --trigger-type <type> flag for the purpose of running only one of an app's trigger types; that could be reused for this purpose as well.

Tracked: #2585

[vdice]

https://github.com/fermyon/spin/releases/tag/v2.6.0 is now out.