Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Packages (next) #2818

Merged
merged 1 commit into from
Nov 18, 2021
Merged

Version Packages (next) #2818

merged 1 commit into from
Nov 18, 2021

Conversation

github-actions[bot]
Copy link
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

master is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on master.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@sveltejs/adapter-cloudflare@1.0.0-next.1

Patch Changes

  • Add new "adapter-cloudflare" package for Cloudflare Pages with Workers integration (#2815)

@github-actions github-actions bot force-pushed the changeset-release/master branch from 6e670d7 to 0d57248 Compare November 17, 2021 23:44
Copy link
Contributor

@Crisfole Crisfole left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I'm not 100% sure what the ~TODO~ line in the .changeset is all about, but it seems like it would get replaced.

@@ -21,7 +21,8 @@
"@sveltejs/vite-plugin-svelte": "1.0.0-next.0",
"@sveltejs/adapter-cloudflare-workers": "0.0.1",
"set-env-action": "1.0.0",
"~TODO~": "0.0.1"
"~TODO~": "0.0.1",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like a potential mistake?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's just an artifact of the project template having that name — it's been there for a long time, it should be harmless

@Crisfole Crisfole mentioned this pull request Nov 18, 2021
@Rich-Harris Rich-Harris merged commit f2e3ca1 into master Nov 18, 2021
@Rich-Harris Rich-Harris deleted the changeset-release/master branch November 18, 2021 16:26
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