Skip to content

Update README.md - fixed workflow start command #3

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.

Sign up for GitHub

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

Merged
axfelix merged 1 commit into from
Oct 3, 2025
Merged

Update README.md - fixed workflow start command #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions exercises/worker-versioning/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,9 @@ the complete version in the `solution` subdirectory.
worker_versioning_demo 2.0 unspecified 1 minute ago
worker_versioning_demo 1.0 unspecified 7 minutes ago
```
4. Now, if you were to kick off another Workflow, for example by running
`npm run workflow a101`, that Workflow would again be handled by the
4. Kick off another Workflow, by running
`mvn clean compile exec:java -Dexec.mainClass="getversion.Starter" -Dexec.args="a101"`
That Workflow would again be handled by the
"1.0" Worker, rather than using your updated code. This is because you
configured this Worker's default versioning behavior to Pinned rather than
auto-upgraded. To update the default version that new Workflows will run with
Expand All @@ -94,7 +95,7 @@ the complete version in the `solution` subdirectory.
--deployment-name "worker_versioning_demo" \
--build-id "2.0"
```
5. Finally, after running this command, go ahead and run
6. Finally, after running this command, go ahead and run
`mvn clean compile exec:java -Dexec.mainClass="getversion.Starter" -Dexec.args="a101"`
to kick off a new Workflow. It will be handled by
your "2.0" Worker, and reflect your code changes, running the second Activity
Expand Down