chore: tweak changeset

[benmccann]

I noticed we didn't mention that this applies to src and srcset as well, which I thought was important to mention. Not sure about the patch/ minor level. Feel free to keep that as patch if more appropriate

[changeset-bot]

⚠️ No Changeset found

Latest commit: 61120b8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 1 package

Name	Type
svelte	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
svelte-5-preview	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 27, 2023 4:28pm

[dummdidumm]

We're making everything a patch right now, not sure if that changes anything. Also, the message only relates to the new thing added, not the already existing things. So I'm tempted to leave it as is.

[benmccann]

We're making everything a patch right now, not sure if that changes anything.

In that case we we should update the changeset for #9609 before cutting the next release. I'll update this PR to do that

Also, the message only relates to the new thing added, not the already existing things

Agreed we should only mention new things. src and srcset were previously hydrated if the client-side value were completely different (i.e. not equivalent when correcting for relative vs absolute). They no longer are after #9662

[Rich-Harris]

src and srcset were previously hydrated if the client-side value were completely different (i.e. not equivalent when correcting for relative vs absolute)

are you sure? All that PR did was apply the same behaviour to href as currently applies to src

[dummdidumm]

I think he meant compared to Svelte 4, where we did this check in prod, too, which we don't in Svelte 5 because the costs outweigh the theoretical benefits of catching a mismatch (for which you get a warning in dev anyway)