Skip to content

Release Version 1#1

Open
Refzlund wants to merge 189 commits intomainfrom
next
Open

Release Version 1#1
Refzlund wants to merge 189 commits intomainfrom
next

Conversation

@Refzlund
Copy link
Copy Markdown
Owner

No description provided.

- Introduced `testing-preview-branch.yml` for branch-scoped Durable Object previews, combined branch deployment and PR comment reporting, and runtime binding verification.
- Added `testing-preview-branch-cleanup.yml` to retire tracked branch preview metadata, delete branch-scoped Workers, and mark GitHub deployments inactive when a branch is deleted.
- Created `testing-preview-pr.yml` for PR-scoped testing previews, updating stable PR comments, and handling cleanup on PR close.
- Updated documentation to reflect new workflows and their purposes, including details on the branch preview lifecycle and cleanup processes.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 11, 2026

⚠️ No Changeset found

Latest commit: 9eb6d63

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.

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

- Added `mergeConfigForEnvironment` function to handle environment-specific configurations.
- Implemented `previews` schema in the configuration to manage cron trigger inclusion for preview deployments.
- Enhanced resource resolution functions to support materialized preview-scoped resources.
- Created tests for deployment strategies to verify behavior of preview-scoped resources.
- Updated integration and unit tests to cover new preview functionality and ensure correct behavior.
- Implement unit tests for D1 migrations in `d1-migrations.test.ts`, verifying immediate migration requests and retry logic.
- Enhance context tests in `context.test.ts` to ensure Durable Object alarm events are established correctly.
- Extend `composed-worker.test.ts` to check for missing fetch handler paths, ensuring explicit errors are thrown.
- Update `routes.test.ts` to improve route discovery tests, ensuring proper configuration and conflict detection.
- Add a new `results.csv` file to track test results and insights.
- Introduce `turbo.json` for task management and build optimization.
…ling

- Rename test cases to reflect command changes from 'cleanup-resources' to 'cleanup'.
- Modify tests to ensure proper warnings and messages are displayed when no matching resources are found.
- Adjust mock fetch responses to simulate live worker environments and remove reliance on preview registry.
- Update test descriptions for clarity and accuracy regarding the functionality being tested.
- Ensure compatibility with new command structure and remove deprecated subcommands.
- Changed pull-requests permission from read to write in multiple workflow files to allow for enhanced functionality.
- Added new typecheck and check scripts in devflare package.json for improved type checking.
- Refactored build-artifacts.ts to isolate Vite build output paths and handle cleanup more effectively.
- Enhanced family.ts to streamline preview scope row creation with improved status handling.
- Implemented path isolation logic in compiler.ts for better asset management during builds.
- Updated plugin.ts to utilize isolated Vite build output paths in the build process.
- Added comprehensive unit tests for build artifact cleanup and GitHub feedback action to ensure robustness and error handling.
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 14, 2026

✅ Documentation PR preview deployed successfully

This pull request gets a stable PR-scoped preview link that is updated in place on every preview run.

Logs and details
.svelte-kit/output/server/entries/pages/_layout.svelte.js              18.47 kB │ gzip:   4.60 kB
.svelte-kit/output/server/chunks/internal.js                           19.02 kB │ gzip:   5.77 kB
.svelte-kit/output/server/chunks/shared.js                             23.90 kB │ gzip:   6.44 kB
.svelte-kit/output/server/chunks/utils.js                              29.10 kB │ gzip:   8.39 kB
.svelte-kit/output/server/remote-entry.js                              35.60 kB │ gzip:   8.02 kB
.svelte-kit/output/server/chunks/runtime.js                            43.37 kB │ gzip:  10.59 kB
.svelte-kit/output/server/chunks/messages.js                           87.43 kB │ gzip:  16.42 kB
.svelte-kit/output/server/index.js                                    130.59 kB │ gzip:  33.53 kB
.svelte-kit/output/server/entries/pages/docs/_slug_/_page.svelte.js   134.93 kB │ gzip:  27.06 kB
.svelte-kit/output/server/chunks/dev.js                               142.87 kB │ gzip:  36.83 kB
.svelte-kit/output/server/entries/hooks.server.js                     170.11 kB │ gzip:  35.52 kB
.svelte-kit/output/server/chunks/content.js                           525.11 kB │ gzip: 133.91 kB

�[33m�[33m[PLUGIN_TIMINGS] Warning:�[0m Your build spent significant time in plugins. Here is a breakdown:
  - devflare (48%)
  - vite-plugin-sveltekit-guard (35%)
  - vite-plugin-sveltekit-virtual-modules (9%)
  - vite-plugin-sveltekit-compile (4%)
See https://rolldown.rs/options/checks#plugintimings for more details.
�[39m
�[32m✓ built in 9.75s�[39m

Run npm run preview to preview your production build locally.

> Using @sveltejs/adapter-cloudflare
  ✔ done
[log] Generated deploy Wrangler config: .devflare/build/wrangler.jsonc
[log] Generated deploy redirect: .wrangler/deploy/config.json
[log] worker devflare-docs-pr-1
[log] Deploying with Wrangler…

 ⛅️ wrangler 4.81.1 (update available 4.82.2)
─────────────────────────────────────────────
Using redirected Wrangler configuration.
 - Configuration being used: ".devflare/build/wrangler.jsonc"
 - Original user's configuration: "<no user config found>"
 - Deploy configuration file: ".wrangler/deploy/config.json"
[success] Preview URL: https://devflare-docs-pr-1.refz.workers.dev
[warn] Deployment verification note: Wrangler completed the named preview-scope deploy for Worker "devflare-docs-pr-1" and exposed https://devflare-docs-pr-1.refz.workers.dev, but Cloudflare did not return a Worker version id. Devflare is treating this branch-scoped preview deploy as successful because named preview workers can lag in control-plane version metadata.
[success] Deployed successfully!

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 14, 2026

✅ Testing branch preview deployed successfully

This workflow publishes a branch-scoped testing preview on every qualifying push, even when no pull request exists. When the branch belongs to an open pull request, the same run also refreshes the stable PR preview comment.

Logs and details
Using deploy command: bunx --bun devflare deploy
Deploy target: preview scope (next)
Bun version: 1.3.12
Node version: v20.20.2
[log]
[log] deploy Shipping to Cloudflare
[log] Reused preview-scoped resources: KV 2 · D1 3 · R2 2 · Queues 4 · Vectorize 2
[warn] Workers Analytics Engine datasets are created automatically on first write, so Devflare does not provision or delete preview-scoped analytics datasets.
[warn] Browser Rendering bindings do not own account-scoped resources, so Devflare does not provision or delete preview-scoped browser bindings.
[warn] Preview Hyperdrive "devflare-testing-next" is not auto-provisioned because Cloudflare does not expose stored Hyperdrive credentials for cloning. Devflare will reuse the base Hyperdrive "devflare-testing" for binding POSTGRES.
[log] Building: devflare-testing-binding-matrix-next
[log] Branch-scoped preview deploy detected (next); omitting shared queue consumers and cron triggers from the deployed Wrangler config to avoid singleton Cloudflare resource conflicts.
[log] Generated bundled worker entry: .devflare/worker-entrypoints/main.js
[log] Skipping Vite build (no effective Vite config found for this package)
[log] Generated deploy artifact: .devflare/build/worker.js
[log] Generated deploy Wrangler config: .devflare/build/wrangler.jsonc
[log] Generated deploy redirect: .wrangler/deploy/config.json
[log] worker devflare-testing-binding-matrix-next
[log] Deploying with Wrangler…

 ⛅️ wrangler 4.81.1 (update available 4.82.2)
─────────────────────────────────────────────
Using redirected Wrangler configuration.
 - Configuration being used: ".devflare/build/wrangler.jsonc"
 - Original user's configuration: "<no user config found>"
 - Deploy configuration file: ".wrangler/deploy/config.json"
[success] Preview URL: https://devflare-testing-binding-matrix-next.refz.workers.dev
[warn] Deployment verification note: Wrangler completed the named preview-scope deploy for Worker "devflare-testing-binding-matrix-next" and exposed https://devflare-testing-binding-matrix-next.refz.workers.dev, but Cloudflare did not return a Worker version id. Devflare is treating this branch-scoped preview deploy as successful because named preview workers can lag in control-plane version metadata.
[warn] Devflare preview registry sync failed: This Worker does not exist on your account.
[success] Deployed successfully!
  • Auth impact: deploy (workspace dependency "devflare" changed)
  • Auth service version: not available
  • Search impact: deploy (workspace dependency "devflare" changed)
  • Search service version: not available
  • Main preview impact: deploy (workspace dependency "devflare" changed)
  • Deployed binding verification: passed
  • Verification mode: CI inspects deployed preview Worker metadata directly when Cloudflare exposes it, and otherwise falls back to the successful named-preview deploy output plus resolved preview config because the testing preview URL is protected by Cloudflare Access.
  • Preview strategy: named preview scope via --preview <branch> so the testing worker family deploys to the same explicit branch target.
  • Auth deploy status: success
  • Auth failure stage: n/a
  • Search deploy status: success
  • Search failure stage: n/a
  • Main preview deploy status: success
  • Main preview failure stage: n/a

@github-actions github-actions Bot had a problem deploying to testing branch preview / next April 14, 2026 12:06 Failure
- Added validation step for documentation branch and PR preview deployments to ensure a valid preview URL is generated and does not match the production URL.
- Implemented a function to resolve the documentation worker name based on the preview scope, allowing for dynamic naming of preview deployments.
- Updated GitHub Actions workflows to incorporate the new validation logic and adjust deployment statuses based on validation outcomes.
- Created a new module for handling worker name logic, including sanitization and clamping of preview scope.
- Added tests to verify the correct resolution of worker names and ensure production URLs are not included in preview comments.
@github-actions github-actions Bot had a problem deploying to documentation branch preview / next April 14, 2026 17:21 Failure
Refzlund added 30 commits April 27, 2026 14:43
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.

1 participant