Conversation
|
🚅 Environment dynamic-apps-pr-296 in rivet-frontend has no services deployed. 🚅 Deployed to the dynamic-apps-pr-296 environment in secure-exec
|
![the-company-company[bot]](https://avatars.githubusercontent.com/in/3874572?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Workflows moved out of
rivetkit/workflowinto the standalone@rivet-dev/workflowspackage. This updates the workflows example and its docs page to the new API.Changes
examples/apps-workflows/fixtures/app/src/index.ts:actor({ run: workflow(async (wf) => ...) })becomesworkflow({ state, actions, run: async (wf) => ... }), withsetupandworkflowimported from@rivet-dev/workflows. Steps and behavior are unchanged.examples/apps-workflows/fixtures/app/package.json: adds@rivet-dev/workflows@1.0.0.rivetkit@2.3.11stays, because the builder uses it to detect an actor app and supplies the platform RivetKit, which satisfies the package'srivetkit >=2.3.11 <2.4.0peer.examples/apps-workflows/package.jsonandpnpm-lock.yaml: add@rivet-dev/workflows@1.0.0so the fixture type-checks in the workspace.examples/apps-workflows/README.md: describes theorderactor (charge, ship, sleep, deliver) instead of a "keyed job actor", and fixes the URL to/apps/order-workflow/to match theorder-workflowapp ID used byclient.ts.docs/content/docs/workflows.mdx: names@rivet-dev/workflowsand links to the Workflows docs.No other
rivetkit/workflowimports,run: workflow(usages, or "RivetKit workflow" prose remain indocs/orexamples/.Verification
pnpm build && pnpm check-types: passes.pnpm --filter @rivet-dev/dynamic-apps-example-workflows check-types: passes.pnpm biome check examples/apps-workflows docs: clean.POST /deploy/order-workflow): the build installs, bundles, and validates the fixture with@rivet-dev/workflows. It then fails at thetarpack step withOperation not permitted (os error 63)on macOS. origin/main fails the same way, so this is environmental and not caused by this change.