Skip to content

Conversation

jycouet
Copy link
Contributor

@jycouet jycouet commented Oct 3, 2025

Looking at https://github.com/sveltejs/cli/actions/runs/18222249563/job/51884670580 there is an issue with the new build. (it's internal thing)

I addapted the script. Should work now.

But looking https://github.com/sveltejs/kit-template-default last deployed was 0.8.21 ! (the one after is 0.9) Maybe an issue with the bot permissions?

Copy link

changeset-bot bot commented Oct 3, 2025

⚠️ No Changeset found

Latest commit: 5e9eac0

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 no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

Copy link

pkg-pr-new bot commented Oct 3, 2025

Open in StackBlitz

npx https://pkg.pr.new/sveltejs/cli/sv@730
npx https://pkg.pr.new/sveltejs/cli/svelte-migrate@730

commit: 5e9eac0

@manuel3108
Copy link
Member

Yeah, it's probably a permission thing. Someone recently suggested somewhere that instead of provide a repo template we should just run sv from the command line, after stackblitz has initialized, similar to what is done with npm install at the moment.
But no clue where I saw that and what the outcome was.

@jycouet
Copy link
Contributor Author

jycouet commented Oct 3, 2025

I think that we should first merge this so that it's at least building wo error when publishing a package. (it's due to the new tsdown)

Then we can see if we remove completely the template or the step or...

Let me know

@manuel3108 manuel3108 merged commit 6553571 into main Oct 4, 2025
5 of 9 checks passed
@manuel3108 manuel3108 deleted the fix/push-to-kit-template-default branch October 4, 2025 04:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants