Release an updated version of 0.13

[levino]

What version of starlight are you using?

0.13.1

What is your idea?

I have patched version 0.13 and would like you to release a new version 0.13.2 with the patches. To this end one probably has to maintain a branch v0.13 where these patches are managed and from which the publication of the patched versions happen.

Why is this feature necessary?

As explained, starlight-blog does not work with starlight@>=0.14 and it does not look like this problem will be fixed right away. I have tested [email protected] with [email protected] and astro@4 and it seems to work. However pnpm complains that [email protected] has the unmet peer dep astro@^3 and I use astro@4 instead (and some sub dependencies). This release would silence that warning and restore order.

Do you have examples of this feature in other projects?

No response

Participation

• I am willing to submit a pull request for this feature.

[delucis]

Sorry for the roadbumps! Given Starlight is still beta software, we probably don’t have the bandwidth to maintain older branches. Instead, hopefully starlight-blog will be able to offer full compatibility with the latest versions soon. I’ll aim to help @HiDeoo get #1175 over the line to move this along!

[levino]

I think the effort to "maintain" a branch v0.13 is very low and the annoyance for new users is harming the project. Taking a couple of minutes to branch out, merge and release a patched version is well spent time. But it is your call. Good luck with fixing the other issue soon. I will come back to this in the new year, if the issues still persists.